Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

FP2.6 windows 3.1 data -> VFP7 can it be done?

Status
Not open for further replies.

Arcadia

IS-IT--Management
Jul 2, 2003
6
RU
Hello,

Currently I have an old FP application running on an old windows 3.1 machine. The machine is starting to die and I'm thinking its time to update the application. Problem is the data in the database is very important.

My question is, is it possible for me to dump all the data currently in the old database and to put it into a new database I've created under VFP7. Secondly, can the new databse contain fields not within the old database? And lastly, are there any issues I need to be aware of while doing this?

The old database has a messed up memo field file too, will this be a problem? The memofield is not as important as the rest of the data however and could be ditched if needed.

Thanks!

- Mike
 
You should have no problems moving the data or even just using the old .DBFs in VFP 7.0. Once you change a tables structure (e.g. add new field type) in VFP 7.0, you won't be able to read the new table in FPD or FPW.

Rick
 
Hi Rick;

Correct me if I'm wrong but doesn't the structure change as soon as the FPD or FPW table is opened for the first time in Visual FoxPro?

Ed Please let me know if the sugestion(s) I provide are helpful to you.
Sometimes your the windshield... Sometimes your the bug.

 
I have a very large application I use both 2.6 and Visual 6.0 files.

You are both right. If you open a 2.6 file fin VFP it does not change the file. If you change the structure, you can not open it again with 2.6.

You can add, change, delete records with a problem.

I actually still develop in 2.6, recompile in 6.0 and run in 6.0.
 
No, about the only thing it might do is prompt you for a code page if FPW hasn't already stored one. Since you can:
SET CPDIALOG OFF
to ignore this in VFP, or set it, and FPD never looks at it anyway.

We have a number of locations that use 2.x DBFs, and both FPW 2.6a applications and VFP 5/6 applications use them (add/change/delete records). While we make sure that the are table alterations are done in the 2.6a app, we've never run into any trouble.

Note: If a table does get "changed", it's a simple matter to have the VFP application do a COPY TO ... WITH CDX TYPE FOX2X to restore it.

Rick
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top