Converting FoxPro 2.6 to Access 2000 - What Challenges Will I Face? 1

[ClementsK]

I have agreed to take on a project that will have me converting a Foxpro 2.6 database to Access 2000. Can someone give me a "heads-up" about what problems/challenges I may face?

BTW - I am seeing a lot in this forum about linking to the FoxPro tables. Is there a benefit to linking vs. converting?

(I am very inexperienced in this area...please bear with me....)

Thanks!
Kim

 

[ErikZ]

I don't know anything about Foxpro. I bet telling the people who do more about your Foxpro database would be a good idea.

Is it on one machine?
Does it have a front-end, back-end?
How big is it?
How many people use it?
All at the same time?
Do you just run reports and querys that don't change, or are there a lot of variables?

 

[newfrontiers]

I am presently developing an Access 2000 front end that links to Foxpro 2.6 datafiles. I can tell you that you will have issues with Foxpro indexes. Maybe since we are working on simular projects we could trade notes or work on them together.

Let me know.

JohnP

 

[Mossoft]

I have recently finished a project that uses an Access 97 front end attaching to, amongst other things, Foxpro database(s). I used the standard Foxpro ODBC driver and had few problems.
If you do decide to attach:
1) Be careful of character set differences, especially high ASCII value (>127) as these may be represented by different characters in Foxpro which uses EBCDIC. I also found that different servers were using different code pages so my app worked on some servers but not others!!!
2) Beware of ODBC connection timeouts (if you intend to use the same DSN for a number of different back end databases). The default value for the timeout is 600 seconds. Any re-use of the ODBC connection during this timeout will re-connect to the original database.

I did not have any problems with indexes.

Good Luck!!

M