Discussion:
FoxPro 2.6 ODBC Driver questions
(too old to reply)
Martin
2004-09-27 08:26:02 UTC
Permalink
We are sharing data from our Clipper/Advantage Database Server App with an
app using the ODBC drivers.

This other app calls a close but the file is still open, also records get
marked for deletion when there are no deletes in the source.

I am trying to help him - any ideas please?

I am already using lots of DBRECALL()
Rick Bean
2004-09-27 12:35:54 UTC
Permalink
Martin,
Are they using the latest (and last) VFP ODBC driver? (It was releaed for VFP 6.0 and it works just fine for older .DBF files - i.e. non-VFP.)

Rick
Post by Martin
We are sharing data from our Clipper/Advantage Database Server App with an
app using the ODBC drivers.
This other app calls a close but the file is still open, also records get
marked for deletion when there are no deletes in the source.
I am trying to help him - any ideas please?
I am already using lots of DBRECALL()
Martin
2004-09-28 15:04:50 UTC
Permalink
Post by Rick Bean
Are they using the latest (and last) VFP ODBC driver? (It was releaed for
VFP 6.0 and it works just fine for older .DBF files - i.e. non-VFP.)
I will ask
Martin
2004-09-29 10:31:32 UTC
Permalink
MICROSOFT VISUAL FOXPRO DRIVER VERSION 6.01.8629.01
Rick Bean
2004-10-04 14:22:52 UTC
Permalink
Martin,
OK, that is the latest version. The only thing that I remember is that Clipper used it's own file locking mechanism that can cause compatibility problems when sharing the data with non-Clipper apps. Also, Clipper could create non-standard .DBF files that the ODBC driver can't handle (e.g. more than 254 fields in the table). Finally, the ODBC driver can't update any Clipper specific index files unless they were using a special driver that created and used Fox compatible .IDX/.CDX type files.

Rick
Post by Martin
MICROSOFT VISUAL FOXPRO DRIVER VERSION 6.01.8629.01
Loading...