• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1769
  • Last Modified:

Delphi vs. FoxPro

I have been developing with Delphi 1 (and a glance at version 2) at it's beginning and was very pleased with it's capabilities. Now, in a different environment, I work with Visual FoxPro 5. We are thinking of upgrading to VFP 6 as soon as it comes out, but voices tell us to not even think about it and migrate to Delphi 3 (and soon 4) as soon as possible before we pop out of VFP due to it's limited DB and Connectivity capabilities, and if we want to be approached seriously in the future.

How will Delphi (4!) handle my legacy Visual FoxPro databases (native?) and is it really worth wile to switch? Are there hard fact sheets with the differences between the two? Can you even compare them, as my experience with Delphi goes back to version 1?

Many thanks for any advise
0
bruck
Asked:
bruck
1 Solution
 
phetCommented:
Delphi will threat Visual FoxPro database as just another DBF file and you can use BDE to access it.
0
 
bruckAuthor Commented:
Sure? Because all my Visual ForPro tables are stored in a database, and are currently unacessible for Delphi in every way I try to open them. Does Delphi use an ODBC driver to connect, or does it have some native connection method? How does it handle the table relationships? Meanwhile I have bought Delphi 4 and I can still not get it to work? Does anybody have a working example. Regarding my other questions. Does anybody have any fact-sheets to compare the two?

Many thnaks
0
 
d4jaj1Commented:
There aren't any fact sheets comparing Delphi to VFP, however, there are looks of technical info on the Inprise site.  a Foxpro driver is included with Delphi 4.  Here's a suggestion though.  Transfer your VFP files into native dBase file format.  Even if you get the Delphi FoxPro driver to work (not an easy task) it will be a bit slower than dBase format for use in Delphi.  Same holds true for linking to Access databases.  

As for table relationships, Delphi handles them quyite well - but you have to set the relationships in Delphi - not the table level.  For example, Delphi will allow you to delete a master record even if detail records exists (ignoring Ref. Integrety) if you don't make teh link in "Delphi".  It will basically ignore this, picture validation and secondary indexes if not set up at teh application level - though it will honor Primary keys.  By application level I mean -in a Delphi Form or Datamodule.  Setting these features in teh Database Desktop or client verion of VFP isn't enough.

Finally, is it worth while to switch.  Definiately - especially if your distributing apps.  The fact teh teh Delphi exe's are 10 times faster than interperted P code should be enough.   A little work in teh beginning to transfer your table to dBASE isn't too big of a problem (a couple of insert queries).

Good Luck.
Any questions , please add a comment.

Jay
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now