This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
programs:odxsql:commandline [2009/11/30 04:29] tdo |
programs:odxsql:commandline [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
| - | ====== OdxSQL Command Line Options ====== | ||
| + | ====== OdxSQL Command Line Options ====== | ||
| + | {{page>:odxsql_bar&nofooter&noeditbtn}} | ||
| OdxSQL can accept the Omnidex Environment as well as several other options. | OdxSQL can accept the Omnidex Environment as well as several other options. | ||
| Line 78: | Line 78: | ||
| The -version option will display the OdxSQL version. Because OdxSQL displays the Omnidex version in the OdxSQL banner and the OdxSQL command displays Omnidex detailed information, use the -version option to verify the particular version of OdxSQL. | The -version option will display the OdxSQL version. Because OdxSQL displays the Omnidex version in the OdxSQL banner and the OdxSQL command displays Omnidex detailed information, use the -version option to verify the particular version of OdxSQL. | ||
| + | |||
| + | == -exit == | ||
| + | |||
| + | Exit after completion of processing the commands in the Use File. This option is typically used in creating operating system batch processing scripts so that OdxSQL automatically terminates. | ||
| + | |||
| + | == -exit_on_error == | ||
| + | |||
| + | Exit if an error occurs. | ||
| + | |||
| + | OdxSQL will normally continue processing OdxSQL commands from a Use file even when a command or syntax error occurs. Seeting the -exit_on_error option will cause OdxSQL to terminate when an error is encountered. | ||
| + | |||
| + | == -nobanner == | ||
| + | |||
| + | Suppress the display the OdxSQL banner. | ||
| + | |||
| + | ==-cloa == | ||
| + | Run OdxSQL using the CLOA client interface. | ||
| + | |||
| + | This option allows the testing of the OmniAccess CLOA API. Although DISC recommends that new applications are developed using the Omnidex ODBC or JDBC drivers, the CLOA API is supported for backward compatibility. When using the CLOA option, the OdxSQL Connect command connects to an Omnidex Client DataSource created with the DSEDIT Windows Client program. | ||
| == -odbc == | == -odbc == | ||