Limitations

<< Click to Display Table of Contents >>

Navigation:  PdxEditor install & specs > PdxEditor specifications >

Limitations

Previous pageReturn to chapter overviewNext page

PdxEditor limitations

Due to the era of the BDE database engine*, a few of the PdxEditor's functions have some limitations concerning path and table namings not accepting non-ASCII characters. This is the case for the following functions:
 • CopyTable
 • View Table Validity Checks
 • View Table Field Types (Native)
 • Restructure Basic: Change Field Names, etc.
 • Restructure Extended: Change Field Names, etc. +/- Required (see below)
Also, reverse Generate SQL CREATE ... will not generate SQL definitions on dBASE tables named with non-ASCII characters, if selecting one of the dBASE Numeric modes (0 ... 3) depending on in depth analysis and recreation reflecting the native dBASE numeric types.

Selecting dBASE Numeric mode 4 (SQL Menu) eliminates this limitation, and will allow propagating dBASE Numeric fields into wider numeric data types as necessary also affecting the Restructure Extended.

See also dBASE: Reverse CREATE modes, SQL data type translation and PdxEditor feature matrix

*: The BDE development ended in the age of the Delphi 5, years before several keywords were redefined - e.g. before String changed from meaning AnsiString into meaning WideString, etc.

__________________________
PdxEditor Application Help, 14 July 2026; © 2010-2026 Niels Knabe