The syntax for starting from the command prompt is described below.
OpenDB.exe {options}
| Option | Description |
|---|---|
| /debug | Starts OpenDB with the debug flag is the same as starting with both the /nospawn and /verbose flags. OpenDB is started in the foreground. Diagnostic messages are displayed, allowing only one connection at a time. |
| /emptystring | Sets option to handle pick null strings as an empty string. Setting this option affects all files. See Creating a super Q-pointer to set this option on a specific file. |
| /MaxColSize nK | Starts OpenDB with the maximum column size set to the value specified in n. Value is specified in Kilobytes (KB). 65536 is the maximum value allowed. |
| /nospawn | Starts OpenDB as a foreground process, but diagnostic information does not display. OpenDB does not respawn child processes and is therefore only able to handle one connection at a time. |
| /nullstring | Sets option to handle pick null strings as SQL NULL. Setting this option affects all files (default behavior). See Creating a super Q-pointer to set this option on a specific file. |
| /ping | Displays the product version number and a list of processes
currently running. For example:OpenDB Version: 3.3 Date: 23 Jul. 2010 TCP Port Process Type --------------------------- 3458 12312 Primary --------------------------- |
| /port #### | Starts OpenDB on a different TCP/IP port number.
OpenDB.exe /debug /port 5800
|
| /verbose | Displays diagnostic messages from OpenDB and the ODBC driver, such as SQL Server. Multiple connections are allowed. |
During development, it is recommended to start OpenDB on a different port number and in debug mode when the current server is in use on a production level. For example:
OpenDB.exe /debug /port 5800
Use these flags to start OpenDB running in the foreground for development and debugging purposes.
debug nospawn verbose