>
>First, they will compile, but the structures of the classlib or form may be irreversibly different from VFP5 to VFP7. But there's a really easy solution for this. Non-visual classes. Source code is not sensitive to the data structure in a code-based class or form definition. If you find that you must go back and that you've migrated irreversibly something that must be rolled back that you haven't provided for with an SCC product, you take the form or classlib, run it through the class browser and emit source code. Face it, text files is text files. And that's all a class defined in code is - source code text.
>
>Do not pass Go, do not collect $200...
>

Forgot something : Go to jail and ...

Ed, thanks. Where I already drew some conclusion that my earlier decision to set it all up in visual classes wasn't the best decision, I think this really is the answer. No danger at all in it. You just pushed me to do it now.

> ...
LOL!