Subject | importing dBase tables via ODBC - problem with rows marked deleted |
---|---|
Author | rick_roen |
Post date | 2010-03-30T14:29:24Z |
I am having a frustrating time importing dBase tables into Firebird using OCBC. I know this is a long shot, but perhaps it will trigger some advise from someone who has faced this problem.
Net ODBC connection string = Driver={{Microsoft dBASE Driver (*.dbf)}};DriverID=277;Exclusive=No;Deleted=1;Dbq=<folder name>
( I have also tried Deleted=0; and left Deleted out altogether)
Query = Select * from [Invoic~1] where Invoicenum = 1234.
This works most of the time, but when the FIRST row of the result set is marked Deleted in dBase, nothing is returned. If the second row is marked Deleted, the other rows are returned.
For those not familiar with the dBase table structure, a deleted row exists in the table until is is Packed (actually removed). Until then it is marked as deleted in the row header, but it is still in place.
Seems like a bug in the ODBC driver, but I haven't been able to find anything on the web about this.
Does this sound familiar to anyone?
If not, can someone recommend a dBase ODBC ng?
Regards,
Rick
Net ODBC connection string = Driver={{Microsoft dBASE Driver (*.dbf)}};DriverID=277;Exclusive=No;Deleted=1;Dbq=<folder name>
( I have also tried Deleted=0; and left Deleted out altogether)
Query = Select * from [Invoic~1] where Invoicenum = 1234.
This works most of the time, but when the FIRST row of the result set is marked Deleted in dBase, nothing is returned. If the second row is marked Deleted, the other rows are returned.
For those not familiar with the dBase table structure, a deleted row exists in the table until is is Packed (actually removed). Until then it is marked as deleted in the row header, but it is still in place.
Seems like a bug in the ODBC driver, but I haven't been able to find anything on the web about this.
Does this sound familiar to anyone?
If not, can someone recommend a dBase ODBC ng?
Regards,
Rick