Since the Import Options dialog is not displayed when the program is driven from an automation script, an options string can be specified in the script. The string consists of comma-separated parameters, which specify the behavior of the various import options. A typical example would be:
"ImportCodePage=1252"
This would set the Unicode Language ID value to code page 1252, or the Western European (Windows) code page.
Option |
Action |
Default |
ImportCodePage |
The name of the ANSI code page to use when importing Unicode data. Valid code page number in the range 0 through 65535. |
"" |
Note: If a companion .SHP file with the same name exists in the folder containing the .DBF file, the .DBF file is assumed to be part of an ESRI-compatible Shapefile set and the defaults as described for the ImportCodePage option in the ESRI Shapefile .SHP Import Automation Options section apply.
Otherwise, the Language ID value stored in the .DBF file’s header determines the code page used. However, if the Language ID value is zero or invalid, the OEM DOS code page determined by the machine’s Control Panel locale setting will be used.
See Also
ASCII Database .DBF File Description