![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello I'm new in Betrieve databases. I've got a strange database without documentation and I have to prepare data export to MSSQL. Today I've tried to find any api for C++ but I couldn't find any useful information how to move data from .dat files. Do you have any information how to "get into" this file and read data?? Trociu |
#3
| |||
| |||
|
|
Hello I'm new in Betrieve databases. I've got a strange database without documentation and I have to prepare data export to MSSQL. Today I've tried to find any api for C++ but I couldn't find any useful information how to move data from .dat files. Do you have any information how to "get into" this file and read data?? Trociu |
#4
| |||
| |||
|
|
BtSearch is a good tool. This does depend on the ".dat" file being an actual Btrieve format data file to work. I've downloaded this tool but it doesn't see my .dat files. I tried with 2 |
|
As to "get info", very little is actually stored in the data files. If it is a Btrieve format file you can depend on getting the record length and data type for any data that falls on an index. If you are lucky the programmer was lazy and wrote everthing in easily decipherable ASCII strings. If you are not lucky it will be some obscure application specific data type. Other than the record segments that fall on indexes, bytes are bytes and the database engine only stores and retrieves them (no translations). So I'm not lucky and only text is in ASCII format. The rest of information is |
#5
| |||
| |||
|
|
On 2004-10-19, Leonard wrote: BtSearch is a good tool. This does depend on the ".dat" file being an actual Btrieve format data file to work. I've downloaded this tool but it doesn't see my .dat files. I tried with 2 verions. As to "get info", very little is actually stored in the data files. If it is a Btrieve format file you can depend on getting the record length and data type for any data that falls on an index. If you are lucky the programmer was lazy and wrote everthing in easily decipherable ASCII strings. If you are not lucky it will be some obscure application specific data type. Other than the record segments that fall on indexes, bytes are bytes and the database engine only stores and retrieves them (no translations). So I'm not lucky and only text is in ASCII format. The rest of information is in binary format. Do you think it is a good idea to make a copy of .dat file, insert one record using application and compare old and new file?? Trociu |
![]() |
| Thread Tools | |
| Display Modes | |
| |