>My understanding at Devcon was that VFP6 would be backwardly compatible to VFP5. But I have recently worked on a couple of classes in a project with VFP6 and when I go to modify those classes in VFP5 I get an error message that the VCX is not an object file. VFP5 will not open these classes at all. When I try to open another class in the same VCX that has not been modified in VFP6, I have no problem. Is this going to be corrected before the release of the production version of VFP6 or is this the expected behavior?
>
>There are projects that have to be worked on by people who will not get an upgrade to VFP6 right away and I can't afford to contaminate them. Currently, my Class Browser in VFP5 is non-functional so I have been using VFP6, but if this is going to make my projects unreadable in VFP5, then I am going to have to work in a crippled VFP5 environment. Does anyone know of a way to fix these classes without deleting them and re-creating them from scratch?
>
>Thanks,
>
>Pamela
>pamela@eagle-crest.com

You can still use your class libraries in 5.0, but you'll need to recompile them. This is a real pain if you are in development environment and one developer is trying to evaluate 6.0 and the rest are using 5.0. So far, I haven't found a way around this little gotcha.