Tech Tip: Resolving Sql Error Code 1101, 1727, and 1701
PRODUCT: 4D | VERSION: 21 | PLATFORM: Win
Published On: April 6, 2026
Error codes 1101, 1727, and 1701 are common when configuring ODBC connections with a 4D database application, especially from a 4D Remote.
For example, the following code, executed from a 4D Remote might cause these errors, given an active 4D SQL Server and a successful login:
The errors indicate that the table in question was not found in the source database specified the SQL LOGIN command, and therefore failed to validate following commands.
To resolve these errors, it is necessary to add the optional * parameter in the command SQL LOGIN. This parameter indicates to execute the SQL code in the source specified in the first parameter. If omitted, the SQL code is executed in the internal SQL engine of 4D. Please read more in the documentation.
For example, the following code, executed from a 4D Remote might cause these errors, given an active 4D SQL Server and a successful login:
| SQL LOGIN("ODBC:4d"; "user"; "pass") If (OK=1) Begin SQL INSERT INTO Table_1 (Field_2) VALUES ('Lorem'); End SQL SQL LOGOUT Else ALERT("ODBC failed") End if |
| 1101 - "Table 'TABLE' does not exist in the database.Failed to validate INSERT command." 1701 - Failed to validate table 'TABLE_1'. 1727 - Failed to validate INSERT command. |
The errors indicate that the table in question was not found in the source database specified the SQL LOGIN command, and therefore failed to validate following commands.
To resolve these errors, it is necessary to add the optional * parameter in the command SQL LOGIN. This parameter indicates to execute the SQL code in the source specified in the first parameter. If omitted, the SQL code is executed in the internal SQL engine of 4D. Please read more in the documentation.