Hi Peter,

Just a general suggestion you might be wise to consider: instead of going straight to VFP7, maybe you should first try making the transition to VFP6 SP5. I think you are likely to run into fewer difficulties, and those you do encounter, you'd probably have to deal with anyway. By the time you're ready to make the move to VFP7 (SP1), you may find that VFP8 is already out, and perhaps you can go straight to there from VFP 6. For your purposes, you could think of VFP8 as VFP7 SP2. (No doubt I'll take some flak for that prediction, but with no clear, open summary of known VFP 7 problems and no plans for another SP, I'll leave it to others to judge this for themselves.)

That isn't to say you shouldn't be making use of VFP7 in the meantime, for the convenience of its developer-oriented enhancements, like Intellisense, Object Browser, etc. But since you seem not eager to introduce any dependencies on new VFP 7 features, it's quite possible that the transition first to VFP 6 would make your life easier.

Mike

>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.
>
>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 ...