Problems and Solutions¶

In this chapter, we discuss the problems that may arise when using DataFlex Reports and solutions for resolving any such issues.

Cannot Open the Language Database¶

DataFlex Reports and the runtime OCX use translation text strings stored in a database named language.db.

The DataFlex Reports designer will default to the built-in English text strings when the database cannot be found or opened. No message is given, but you will find all languages in the language pull-down grayed out.

If the OCX needs to find a text for translation and the language.db cannot be opened, you will receive a message informing you of this, and then the OCX defaults to the built-in English text strings. The language database is used for text strings like Page N of M and for errors generated by the database driver or errors generated internally in the OCX. If a translation cannot be found, the system defaults to the built-in English text string.

The language.db should be present in the same folder where the DataFlex Reports Workstation Runtime is installed.

Cannot Open DR.db¶

DataFlex Reports makes use of an SQLite database to store the repository, External Library Functions (ELF), and label definitions. The database is also used when the report uses RDS (Runtime Data Source). The file must be located in a sub-folder of "Program Data" or where the DataFlex Reports Workstation Runtime is installed. Ensure that the current user or the account under which the WebApp is running has write access to the file.

Unable to Instantiate COM Object¶

The DataFlex Reports designer uses three CodeJock ActiveX modules, its own runtime OCX, and an editor OCX. If any of these COM modules are not registered correctly on your machine, you will encounter this error. At the end of the error text, you will see a COM error code, which is a hexadecimal number indicating why the COM object could not be instantiated. A couple of common codes are:

Consult the systems administrator to resolve the above problems.