identify DBF Type

[AUGE_OHR]

hi,

in Header of DBF are Information what Type of DBF it is

Code: Select all

      CASE nType = 2    //  02h   FoxBASE
      CASE nType = 3    //  03h   Foxpro/dBASEIII/Ads/Clipper no memo
      CASE nType = 4    //* 04h   dBASE IV w/o memo file
      CASE nType = 5    //* 05h   dBASE  V w/o memo file
      CASE nType = 7    //* 07h   VISUAL OBJECTS (first 1.0 versions) for the dBASE III files w/o memo file
      CASE nType = 48   //  30h   Visual FoxPro/Ads
      CASE nType = 49   //  31h   Visual FoxPro, autoincrement enabled
      CASE nType = 67   //  43h   dBASE IV SQL table files, no memo
      CASE nType = 99   //  ???   dBASE IV SQL system file no memo
      CASE nType = 123  //* 7Bh   dBASE IV with memo
      CASE nType = 131  //  83h   FoxPro/dBASEIII/Ads/Clipper with memo
      CASE nType = 135  //* 87h   VISUAL OBJECTS (first 1.0 versions) for the dBASE III files (NTX clipper driver) with memo file
      CASE nType = 139  //  8Bh   dBASE IV with memo
      CASE nType = 142  //* 8Eh   dBASE IV w. SQL table
      CASE nType = 179  //* B3h   .dbv and .dbt memo (Flagship)
      CASE nType = 203  //  0xCB  dBASE IV SQL table files, with memo
      CASE nType = 229  //* E5h   Clipper SIX driver w. SMT memo file.
      CASE nType = 245  //  F5h   Foxpro 2.x/Ads (or earlier) with memo
      CASE nType = 251  //  FBh   FoxBASE

so i can found out which RDD is to use with "VIA".

now i got the Problem, with DBFNTX, to find out if it contain OEM Sign ... how

[dragancesu]

no need, it's a clipper index

https://www.clicketyclick.dk/databases/xbase/format/

[AUGE_OHR]

hi,

no need, it's a clipper index
https://www.clicketyclick.dk/databases/xbase/format/

sorry i don´t mean DBFNTX as Index, i mean Type of DBF that use NTX

Code: Select all

File     SCANDBF.DBF
DBF Type          3 Foxpro/dBASEIII/Ads/Clipper no memo
		DBFNTX/ADSDBE : NTX
is Ansi 	 .F.
Codepage DOS 850

i got Information from Byte 30 of DBF Header which point to Codepage (if have)

this seems a old DOS DBF create with Cl*pper or DBU.EXE (DOS Version)
they can contain "Umlaut" ( CHR() > 128 ) which harbour / HMG did not recognizance in BROWSE ( need ANSI or Unicode )

[AUGE_OHR]

hi,

found this ( have print as PDF )

DBF_Repair.zip

(298.82 KiB) Downloaded 151 times

it talk about Byte 29 which hold Codepage and include Source to "repair DBF" (not tested)
so i test both and most got DOS 850 or 0 for "old OEM DBF"

---

using FIELDS or ROWSOURCE you "just" can use FIELD Name ... without ALIAS
so it is not possible to use OEM -> ANSI conversation "on-fly" with harbour / HMG like Xbase++ do in DBE ( RDD )

i think i will convert all DBF for new Project to avoid Problem with German "Umlaut"