Hi Neil,

I don't see any discrepency between VFP help for SYS(2029) - Table Type and actual results. Can you modify the code below to show the problem you are describing?

CLEAR
CLOSE DATABASES ALL
lcCmd = [CREATE TABLE Testxxx ( cc C(20), mm M] + [)]
= ShowTableType(lcCmd,48) 
lcCmd = [CREATE TABLE Testxxx ( cc C(20), mm M] + [, ii I AUTOINC] + [)]
= ShowTableType(lcCmd,49) 
lcCmd = [CREATE TABLE Testxxx ( cc C(20), mm M, ii I AUTOINC] + [, vv v(20)] + [)]
= ShowTableType(lcCmd,50) 
lcCmd = [CREATE TABLE Testxxx ( cc C(20), mm M, ii I AUTOINC] + [, qq Q(20)] + [)]
= ShowTableType(lcCmd,50) 
lcCmd = [CREATE TABLE Testxxx ( cc C(20), mm M, ii I AUTOINC] + [, ww W] + [)]
= ShowTableType(lcCmd,50) 
RETURN
*-------------------------------------------------------

FUNCTION ShowTableType(tcCmd, tnExpected)
&tcCmd
USE 
lnTableType = ASC(FILETOSTR("Testxxx.dbf"))
?
? lcCmd
? "Table Type: " + TRANSFORM(lnTableType )
IF lnTableType <> tnExpected
	?? " - Expected ", TRANSFORM(tnExpected)
ENDIF	
RETURN

>I have been testing Varchar, Varbinary & Blob field types in VFP9.
>
>One thing I have noticed is that the File type in the DBF Header is only being set to 0x32,
>which is the setting for Auto-increment, and not 0x43 as stated in the specs.
>
>Is this going to cause problems, especially when you have Autoinc and say a Varchar and a Blob field in the same table and the Type set to 0x32, and not 0x43 as it should be.