Thanks for the reply, Don. My challenge is that the conversion needs to happen unattended at about 1 AM every morning. Any ideas on how to accomplish this? This may actually not be an issue: The table structures only rarely change. I might be able to get away with converting the DBCs once and then only copying the tables each night. Sounds like an interesting experiment, anyways.

-Bernie

>>Since it's easy to open a 3.0 DBC in the 6.0 development environment, I assumed I would only need to copy the database files and allow them to be converted automatically when the 6.0 applications run. Unfortunately, when I try to access the tables from a compiled VFP 6.0 .EXE file on the new server, I get the error: "The database for table [pathtodbf] could not be opened..." I tried running a mini app againt the DBCs to simply OPEN DATABASE [myDBC], but that produced the error "Object file [pathtodbc] was compiled in a different version of FoxPro." Hopefully, there is an easy answer to this that is simply eluding me at the moment. BTW, the VFP 6.0 development environment is not on the server, only the runtime files. We'd like to keep it that way if possible.
>>
>>Thanks in advance,
>>
>>-Bernie Falor
>>Library Video Co.

>Since you're copying your 3.0 data files to a 6.0 copy, all you should need to do is open the copy with VFP6 development and COMPILE DATABASE xxxx. This should stop the problem of the runtime saying "previous version"...
Fred