>>>Description :
>>>
>>>This is not much about compatibility as such, but strange enough to mention (read : never saw it before);
>>>
>>>After applying some changes in one of the (visually created) VCXes, suddenly an adjustment wouldn't save without further notice. No matter what I tried, after re-reading the method into the editor, the change had gone.
>>>
>>>Opening the MyVCX.VCX (via Project Manager) in VFP5, and beginning to edit the class concerned, showed a "MyVCX.VCX is not an object". A rather strange message for what I intended to do I'd say.
>>>
>>>Opening the VCX in browse showed nothing strange, and my adjustment wasn't there too.
>>>
>>>Solution :
>>>
>>>Not a solution of the cause, but the solution to continue, appeared to be a PACK of the VCX. Since there weren't any deleted records in there, somehow the Memo file must have got corrupted. The Pack, though, didn't say anything. It just did its work.
>>>
>>
>>Are you running on Win2K without SP2 or SP3 installed?
>
>Ed, I'm afraid I am (SP1). So I guess I missed something, uh ?
>

Yep - there's a not-so-subtle bug with Win2K's deferred disk caching that results in VCT/SCT files not actually being written to the media except on a normal shutdown and termination of Windows; another not-so-subtle bug in the disk device manager caused IDE drives to reenable their write caching after each reboot even if you disabled it! The result; lots of trashed memos for forms classes and the like. Fixed in SP2 of Win2K.

>>
>>>Remark :
>>>
>>>It wasn't caused by opening/changeing the VCX in VFP5 or so.
>>>After the Pack the class concerned in the VCX did normally open in VFP5 again.
>>>
>>>Update :
>>>
>>>Well, after quitting VFP7 once and restarting it, now all the methods of the class are gone. Something's going on here ...