Thanks lots... I just wish I could have found it in the documentation... (This does not mean it is not there, I just didn't find it.)

Mike

>Mike,
>Whenever you open a VFP3 database with a newer version of VFP it will convert the DBC to the newer version. You don't have to make any changes for this to occur. As you've found the fix is to recompile in VFP3.
>
>>I have an interesting conundrum.
>>I have a VFP3 application (2 years old and still going stong, yah Fox) and am writing a new one in VFP6.
>>This application is totally separate from the older one, however...
>>I have opened one of the tables in the old one.. to do a browse.. and then I close it.
>>
>>When the users try to use the VFP3 application, they get a the database was compiled on an earlier version of Foxpro, or something like that.
>>
>>To fix it so the users can use the database again, I start VFP3 open the database and compile it. The database is invalid otherwise.
>>
>>I know there are a number of stored procedures in the VFP3 dbc. Could this be the cause of the problem? I know I don't intentionally change or compile the dbc in VFP6, but could it be happening behind the scenes?
>>
>>I will be using a view to look at this data in the final version of the new app., but until then???
>>
>>Just curious,
>>TIA,
>>Mike