Kelly,

On the whole, I believe that the application will upgrade from Version 3.0 to 6.0 without too many problems. The size of the application could have some bearing on potential issues.

There were cosmetic issues in upgrading from Version 3.0 to 5.0 and control positions and font attributes (at least when using native VFP controls) were changed during conversion. This may have been corrected in 6.0 converter.

If you have any formsets that contain a single form, the converter will remove the formset container, but not any underlying code that referenced the formset (i.e. THISFORMSET). These references will have to be corrected if they exist.

Also, the VFP native classes have acquired additional properties and methods over the years and it is possible that some user-defined custom properties and methods now conflict with native properties and methods having the same name. This is admittedly a remote possibility, but I raise it as I know of a specific instances where these conflicts occurred (no, not my application).

If you can get a copy of the Version 3.0 project, open it in 6.0, build it and, assuming it builds OK, run it to see what else has to be done, if anything.

Hope this helps,

John