Hi Troy ---

Physically copy the VFP 3.0 database files (DBC, et al) to a backup directory (for safekeeping) then do COMPILE DATABASE {database}. This will bring it up to VFP 6.0 and then you can whatever else you need. Should something fail, you can restore the VFP 3.0 database container from backup.


>When I send my VFP application to clients, the setup program always calls a conversion program I wrote. This conversion program moves the endusers' old data to a new database which has any new fields and tables added. It also contains code that changes some field names and field sizes when needed. I've never had a problem with it- until now.
>
>For this next release I'm moving from VFP 3.0 to 6.0.
>Now when my app attempts to open the old database for conversion it gets that error message about it being compiled under a different version caused by the stored procedures.
>
>I have found two solutions to this problem but I don't like either because they involve significant code changes.
>
>Solution #1. Remove the stored procedures. Convert it to a database without stored procedures then convert it again to VFP 6.0.
>
>Solution #2. Open tables independent of the database container.
>
>Any other solutions?
>
>Thanks.