I am about to enbark on an application using a Visual FoxPro database accessed
using ADO and ODBC.

Are there any querks to using this setup?

It seems that rather than use SQL Server I can used the 'free' VFP database
that comes with the Developer Suite.

In trials it is very much quicker than the same setup with Jet (Access).

Is there any advice you can give?

Nicholas Jory
http://www.*-*-*.com/

I would strongly advise you not do this type of solution.  Access,
FoxPro, Paradox and Dbase are not client/server databases. As such you
do not get the performance or the robust system that you need in this
type of application.

I have been burned on several system like this. If this system can not
justify the budget to be built with Oracle, SQL-Server or Informix than
I would suggest you evaluate the true ROI on the project. You have a far
lower TCO in the long-term with a true DBMS system.

The problems with local databases:
 * few have row level locking most support only page locking
 * fox and dbase require packing, which VB, ODBC, OLE DB and ADO cannot
do
 * replication / backup - if your data is damaged in any of these tools
good luck recovering the data! In many case, you will need to restore an
older database copy for a backup. FoxPro has no offical way to recover
data. You have to buy a third party tool. Microsoft does not support any
of this. It is very common for FoxPro to update header incorrectly
corrupting the database.
 * multi-user - these are not multi-user systems. Access will often get
confused with different users and corrupt the database.

Of course, this is IMHO, but move forward with caution

Jeff Duska

Hi,

I have to agree with Jeff in the strongest terms possible. Currently I'm
supporting a foxpro based PC application and my holy opinion is that foxpro
is just not a viable technology for commercial software. Data corruption
happens frequently!

Given a mandate of "no money for databases" I would choose Access over
foxpro in a second (this might be a case of the grass being greener). I have
seen multiuser apps written using access that actually work, stayed up, and
no data corruption. I have never seen a foxpro app do that.

Remember that what ever database you choose: It's only worth what you paid
for it.

Rob