Here are descriptions of some possible errors when working with databases.
Database opening error messages
ConErr-00001: Format not found.
The application cannot detect the data format of the database you are trying to connect to using ADO interface. Please ensure that you specified the correct database kind and database driver.
ConErr-00002: Unknown database:...
The application cannot detect the database you are trying to connect to using BDE interface. Please ensure that you specified the correct database name.
Remote database connection related error messages
Connection was lost.
Connection is lost.
Connection is not defined.
[Errors with empty text]
The application lost connection to the database or the database connection is unstable. The reason can be a network problem, server shutdown, etc.
If the connection was restored (or if you think it was restored), you can try to repeat the unsuccessful operation. For example:
- If you receive the error when executing a SQL query, just execute it again.
- If you receive the error when opening the list of database objects, click the Refresh button above the Object Browser.
- If you receive the error when switching a tab in a set of tabs, switch to the previous tab and then return to the problem tab again.
- and so on.
If nothing helps, you might need to close the database and connect/open it again.
Export related error messages
ExpErr-00001: File [FILE] already exists.
The error occurs when you export data to a file using CREATE+INSERT export mode, and the target file already exists. To resolve the problem, please change the file name or export mode.
ExpErr-00002: Table [TABLE] already exists.
The error occurs when you export data to a table using CREATE+INSERT export mode, and the target table already exists. To resolve the problem, please change the table name or export mode.
ExpErr-00003: File [FILE] does not exist.
The error occurs when you export data to HTML using template, but the template file does not exist. To resolve the problem, please create the template file or correct the template file path.
ExpErr-00005: Critical error count reached.
The error occurs when the number of errors during the exporting process reaches the critical level you specified in the export options. To resolve the problem, analyze and fix the errors or increase the Critical error count option.
ExpErr-00006: Unknown source field name:...
The error occurs when your export field mappings contain a field which does not exist in source dataset.
Reports related error messages
VLR-00001: Invalid XML description of the dataset.
XML description of the report dataset is invalid. Please follow the rules for XML descriptions of report datasets and correct it.
VLR-00002: Folder does not exist:...
The folder to which you refer does not exist. Please correct the reference.
VLR-00003: File does not exist:...
The file to which you refer does not exist. Please correct the reference.
VLR-00004: Invalid report structure.
The report structure is invalid. Please ensure that the file is Reportizer/Database Tour Pro report file and that you use correct Database Tour Pro version to open it.
VLR-00100: Invalid sort order.
The sort order property of the report is invalid. Please correct it.
VLR-00101: Invalid filter condition.
The filter property of the report is invalid. Please correct it.
VLR-01000: Sort error:...
An error occurred while trying to apply the sort order. Please correct the sort order property of the report.
VLR-01001: Filter error:...
An error occurred while trying to apply the filter. Please correct the filter property of the report.
VLR-10001: Invalid report engine version:...
Please ensure that the file you are trying to open is Reportizer/Database Tour Pro report file and that you use correct Database Tour Pro version to open it.
Other error messages
Internal error in the application. If the error is repeatable, please let us know the details.
Out of memory.
This message means there is no enough operating memory to perform the operation. This error occurs in the following cases:
- You opened too many windows. Close some windows to reduce the memory usage.
- You are scrolling down too big dataset. Rewrite your SQL command to return less number of records.
- You are exporting too big dataset. In many cases, exporting a big dataset requires loading large number of records into operating memory. To avoid such a problem, try to use FD interface whenever possible and export big dataset as a table (the table must have a primary key): in this case the exporting process will be slower, but the memory usage will be stable during the process. If you are exporting a SQL query result, try to select less portions of records. There is an detailed instruction.
The requested operation requires elevation.
This message means the user does not have permissions to do the requested operation. Try to run the application as Administrator.
This message may appear in the following cases:
1) Database file does not exist, corrupted or network connection (if the file is located on another machine) is unavailable.
2) You are trying to open an Interbase database file (.GDB, .IB) when InterBase Client or InterBase Server is not running.
Table is read only.
This message is shown, when you are trying to modify a read-only data set or trying to set an editing mode for non-editable data set.
Table is busy.
This message is shown, when you are trying, for example, to delete or restructure the table, which is used by another open data set in Database Tour or another user (e.g. in other application(s) on the same or another computer).
Table does not exist.
This message may appear, for example, when you are trying to delete a table, which does not exist, by using SQL, or a pseudo-table (so called view) by choosing Table | Delete. To delete such table use the following query:
DROP VIEW <table_name>
Record locked by another user.
This means that the current record locked by another user (from another computer or another application). You cannot edit this record until it unlocked. You may press ESC, select another record and try to repeat unsuccessful operation.
You are are trying to add a duplicate record into the field(s), which have unique key. For example, in Paradox table with primary key (which always unique) you cannot add record, in which field values duplicate already existing record with the same field values.
Capability not supported.
This means that the function you activated is not supported in this context. For example, this message appears when you are trying to refresh, sort or empty an ASCII table (for BDE connections), because these capabilities not supported for this data type.
There is no default printer selected.
There is no printer installed on your machine. If you installed the printer after the application started, then you must reload Database Tour to update the printer settings.
The printer selected is not valid.
This means the printer driver is not valid or your selected printer is the network printer and currently inactive. You can try to solve the problem and then reload Database Tour.
Unknown data format.
Such an error may appear, for example, when you are trying to open report from corrupted report template. This corruption may be done by manual editing the template (deleting the necessary data, specifying an unknown report version etc.). Try to correct the data and repeat the operation.
Operation must use an updateable query
Such errors appear in some operations with data in ADO databases. For example, you may meet it when inserting or updating records in a Paradox table, which has no primary key.
Syntax error in [CLAUSE] clause
If you get such error on executing an SQL query, then this means you have some mistakes in your SQL statement. So, you will need to correct the statement. However, sometimes such errors appear when opening tables in ADO databases. For example, the tables in some XLS files may appear incorrectly named and ADO is unable to open the associated query. In such cases you may try to open not the table itself, but SQL query like
SELECT * FROM <table_name>
where <table_name> is the name of table you wish to open. If the error continues, try to use alternative table name, for example, enclose it in square brackets or quotes.
An error occurred while attempting to initialize the Borland Database Engine.
Interface mismatch. Engine version different.
BDE not available.
These messages mean that you have not BDE on your computer or its version is less than 5.0. To work with databases via BDE, you must install BDE version 5.0 or above.
Cannot load an IDAPI service library.
This message may appear in the following cases:
1) File (library) does not exist.
2) Not enough memory to load the library.
3) You are trying to open through BDE an MDB file, but you have not installed Microsoft JET Engine (from Microsoft Access or FoxPro) or its version is not supported by the installed BDE version.
For example, if you have not installed the Microsoft Access 95 and your BDE version is 4.0, then probably you cannot access MDB files by using Database Tour even if you have Microsoft Access 97 or later. Possible solution (but author does not guarantee that it is the best solution) is to install a newer version of the BDE. Read the BDE documentation also.
Another example - you use an improper MSACCESS driver for accessing MDB files. Try to change it (if it is possible) in the BDE Administrator utility, Configuration | Drivers | Native | MSACCESS | Dll32 item.