Migrating Foxpro2.6 for DOS

[gazza11]

I am very competent with Visual basic (6.0), Access, SQL but totally incompetent with FoxPro. A good friend has a relatively complex database that was created in Foxpro 2.6 for DOS. he has been using it since early 1993 and would now like to have a couple of minor changes included. My friend contacted the fellow that wrote the database and he advised that he can no longer support it (the database) as he has retired and being mid 70s is not really interested.

I am wondering whether:
1. The Foxpro 2.6 for DOS database can be easily migrated into a later version (even VB or Access).
2. Is it possible to convert the DOS screens to VB forms.
3. What are the options for migration to later version etc

 

[tilltek]

If you're already competant in several computer languages, especialy basic, you would be better off to pick up a bit of Foxpro syntax and doing those minor changes to the existing code. Let's face it. It's worked OK for ten years. Why mess with it more than you have to.
You could probable do it with a good book BY your side and the TecTips team ON your side.
Ken F

 

[rgbean]

I fully agree with Ken's comments on making a few minor changes. To answer your specific questions:
1. The data tables can easily be linked to by Access.

2. No - there are no utilities that I'm aware of, mostly because the concepts are quite different. DOS concepts are quite diffent from the Window philosopy the Access and VB use.

3. While you could run the FP DOS application under VFP 7.0, you probably won't be happy with the looks, and you won't be able to use almost all of the native VFP capabilities without major changes. Most all who have tried the "conversion" tools avaiable suggest that re-writing the application from start would have been quicker and with a better end product.

Rick

 

[JRB-Bldr]

The advice provided above is excellent.

If the changes are truly MINOR, leave the application in FPD, learn a bit of FP coding (should be easy for someone with your experience), and make the changes in the "as is" application.

As far as upgrades, the easiest "upgrade" would be to FP 2.6 for Windows (

http://www.emsps.com/oldtools/msfoxv.htm

). In spite of its being a "dinosaur" and no longer being supported by Microsoft, it is still an excellent product and will run in all current Windows OS's. VFP is even better, but it is more complicated to "upgrade" (see Rick's comment above).

The FPD code will run "as is" in FPW. While not required, most people who make this transition eventually re-design the user screens to look like Windows application screens and re-design the reports to utilize the Windows printers (instead of LPT1: and COM1: printers).

One of the biggest challenges I have found in migrating FP applications to VB is that VB just doesn't do data manipulation like Foxpro. VB appears to treat data as an "alien" object and relies on external SQL operations and stored procedures on "intelligent" back ends to "massage" the data into the necessary format. FP and VFP can do it locally within the program thereby making it extremely more powerful for complex data calculation/manipulation applications with related, normalized data tables.

Good Luck,
JRB-Bldr
VisionQuest Consulting
Business Analyst & CIO Consulting Services
CIOServices@yahoo.com

 

[gazza11]

Many thanks for the replies. This is my first use of this forum and I am impressed with the quality of the assistance provided.

Looks like more reading for me - as I delve into Foxpro.