>>Hi Gil,
>>
>>Try the following:
>>
>>Create a dummy bizobj.
>>Open the builder for it and add to it one of the damaged dataenvironments.
>>Save it.
>>
>>Now open the dataenvironment and take a look at the cursor(s)'s properties to see if this fixed it.
>>
>>Jim and I were hit by this a few months ago and if I recall correctly, this solved the problem.
>>
>>Hope it helps!
>>
>
>Alex,
>
>Try this:
>Create a new custom class -
>"CREATE CLASS mycustomclass OF Mycustom.vcx as custom"
>Add 2 properties - 1. cCursorSource 2. Cursorsource
>Edit the properties by deleting the default .F. [changing them to (NONE)]
>Close and Save this new class
>
>Use ClassBrowser to modify your new class. Look at your two added properties.
>
>Think VFP has a problem with the term 'cursorsource' ?
>
>Change your current directory and edit the two properties back to (NONE).
>Save and close. Open again and be amazed.
>Change to another Drive and do again.
>
>Finally, use VcxEdit to edit and save the properties and open it with class browser or File/Open.

Gil,

I tried your test. Yikes! Thankfully, I don't run into this problem often. BTW, did you try Alex's suggestion? I can't remember if that worked or not.