Entity Developer 1.0.53 forgets property settings

[pm620wh]

Hi

My Environment:

I am developing on Windows XP using mySQL 5.0.45
I'm using the Entity Developer 1.0.53 in conjunction with VS2008 (with VB)

In my model, I am changing the 'Update Check' property to 'Never' for certain fields in each table.

Each time I load the model into the Entity Developer, the 'Update Check' property reverts to 'Always' and I have to go through every table and reset the property for each affected field - very annoying.

Is this working as designed?

Any help would be greatly appreciated.

[johnvms]

Wanted to mention I'm having the exact same problem.

My environment: Vista 32bit SP1, running MySQL 5.1.31, VS2008 Std (C#), Entity Developer 1.0.53

I have a simple model, and anytime I change the 'Update Check' property it reverts back to 'Always'. It also appears the Read Only property is ignored....

And yes, it is very, very annoying...

[AndreyR]

This problem is fixed in the upcoming build of Entity Developer.
Follow the announcements on the forum.

[pm620wh]

Hi

Thank you for the feedback.

Here's the million euro question .... you've guessed it ... any idea when the next version is due out please (to the nearest month)?

Thanks once again.

[AndreyR]

The new build is available.

[pm620wh]

Hi

I downloaded the latest version of dotConnect 5.0.29 with the Entity Developer 2.018 to get the fix to a previous posting "Entity Developer forgets property settings". The bug still appears to exist (unless I'm missing something).

If I set the 'Update Check' property to 'Never', when I close the program, relaunch and open my project, all the settings for this property on all my tables is set back to 'Always' (I am saving my project changes of course).

Everytime I modify my database (as I am still developing the schema), I have to modify all the tables AGAIN and AGAIN. This is very frustrating.

Your response to my previous posting stated this bug was fixed. Can you help me please as I now dread having to make changes to my schema.

[pm620wh]

My sincere apologies, it does work. I have some tables way off view on the virtual page that I had missed the first time round when upgrading my project.

Sorry