The program supports dBase III, dBase IV, FoxPro, VFP and dBase Level 7 formats. We tried to uninstall old ‘.12.0′ and ‘.16.0′ drivers. Allows you to convert your dbf files to MDB (Microsoft Access) format. Actually, new ‘.12/16.0′ drivers which can support 64 characters file name are now available in Office365 Build 1807 and later version. It seems ‘.12.0′ and ‘.16.0’ drivers which are now available to download have 8.3 file name limitation. And even captured TTT to confirm the file name was not truncated to 8 characters before calling ‘.12.0′ driver. Therefore, we captured process monitor trace and found SQL SERVER was looking for ‘F:tempSJSMX001.DBF’ instead of ‘F:tempSJSMX00103.DBF’ We are quite sure that SJSMX00103.DBF is under ‘F:temp’. If ‘SJSMX00103.DBF’ is not a local object, check your network connection or contact the server administrator.”.Ĭannot get the column information from OLE DB provider “.12.0” for linked server “(null)”. Make sure the object exists and that you spell its name and the path name correctly. OLE DB provider “.12.0” for linked server “(null)” returned message “The Microsoft Access database engine could not find the object ‘SJSMX00103.DBF’.

SELECT * FROM OPENROWSET (‘.12.0′,’dBase 5.0 HDR=YES DATABASE=F:temp’, But they found when DBF fine name is longer than 8 characters they received below error: They need to import a lot of DBF files into SQL SERVER. See the original author and article here.

Microsoft dbase driver dbf download