Mike,

I used to work with Btrieve files. It's been a while though. We've used DBFTrieve because at that time, the ODBC drivers for Btrieve were nicely put, unusable.

DBFTrieve takes a while getting used to. It's a bit like working with low-level file functions and xBase commands. You have functions like b_use, b_seek, b_skip, b_delete, b_append, b_replace, etc. The actual record is converted to a character string and stored in an array. To read/write a field, you have to map to the position of the field within the record.

Btrieve is storing metadata about the tables in DDF files. If you have these DDF files available, then I suggest that you try ODBC. Maybe the drivers have improved since I've last used them. Without the DDFs, however I'm afraid you have to use DBFTrieve.

You can send me a DAT file and if you have, the corresponding DDFs. If you don't have the DDFs, you will need to tell me the structure of the table. I'll have a look and try to convert it. I can also send you some sample programs that should get you started with DBFTrieve should you decide to go this way.

>Hey all,
>
>I'm trying to convert a Btrieve file to something I can use. I'd like to use DBFTrieve, but we don't wanna drop $350 on something we're not sure will work.
>
>Whats the best way to convert these files? I think I have teh DATs, do I need supporting files?
>
>If anyone has DBFtrieve, how does that work? If possible, can anyone test out converting my files so I can see it work before I buy it?
>
>Thanks