I need to read and write DBISAM v2.00 tables. I have seen elsewhere on this forum that it doesn't seem possible to do this with the ODBC drivers (even the older ones), is that right?

If that is the case, is there any source code available for reading and writing these older version files? Or what might be even more useful is a file format description that would show the specifications for the full file formats, including headers, record format, index and blob file formats etc. Then I could simply write my own very basic code for reading and writing these files.

Note that I cannot upgrade the files, because they are still being used by a third-party application, and we have no control over their method of database access.

Thank you so much!
Richard

Richard,

I was not around for v2 but as per Chris Holland the v2 odbc did not
have write capability so odbc is not an option.

If you can't get the 3rd patty vendor to upgrade (v2 goes back to 2001)
then  Elevate Software does sell the DBISAM in source code version so
you can contact them at sales@elevatesoft.com to inquire about obtaining
v2 version with source code.

Depending on what you need to do you can use it to figure out the file
format or it might be easier to just use the components to write a
light-weight dll so you have full edit capabilities to the v2 database
from any language that supports using external dlls.

Raul

On 4/4/2012 10:02 AM, Rich wrote:
> I need to read and write DBISAM v2.00 tables. I have seen elsewhere on this forum that it doesn't seem possible to do this with the ODBC drivers (even the older ones), is that right?
>
> If that is the case, is there any source code available for reading and writing these older version files? Or what might be even more useful is a file format description that would show the specifications for the full file formats, including headers, record format, index and blob file formats etc. Then I could simply write my own very basic code for reading and writing these files.
>
> Note that I cannot upgrade the files, because they are still being used by a third-party application, and we have no control over their method of database access.
>
> Thank you so much!
> Richard
>