>Hi Tamas,
>
>Your table type is correct. In the VFP Help on the table structures formatting is messed up. The file type value belongs to the description in the next line, not the one it appears in. See SYS(2029) - Table Type for the correct values.
>
>>I've just noticed something which really bothers me.
>>When I was checking the file structure of one of my tables, I found that the first byte indicates '31', which would mean - according to table header record structure in the help - a simple Visual FoxPro file. The fact is the table was created as an autoincremented one, and as it is, that byte should be '32' as it is written in the help. What did I miscalculate?
Sergey,
Thanks. In VFP8 Help I see
File type:
0x02 FoxBASE
0x03 FoxBASE+/Dbase III plus, no memo
0x30 Visual FoxPro
0x31 Visual FoxPro, autoincrement enabled
0x43 dBASE IV SQL table files, no memo
0x63 dBASE IV SQL system files, no memo
0x83 FoxBASE+/dBASE III PLUS, with memo
0x8B dBASE IV with memo
0xCB dBASE IV SQL table files, with memo
0xF5 FoxPro 2.x (or earlier) with memo
0xFB FoxBASE
which contradicts to
MS Help onlineand your message in another thread
Re: Table opened in F26 vs VFP... Thread #
1124531 Message #
1239421. What is the correct information?
Looks like VFP8 Help is correct, I've checked two files in hex editor I got from
http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htmThanks a lot in advance.
If it's not broken, fix it until it is.
My Blog