This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
important_information [2009/11/29 22:15] tdo |
important_information [2012/10/26 14:19] (current) |
||
|---|---|---|---|
| Line 33: | Line 33: | ||
| Use the following guide to determine whether to use an Omnidex XML Environment or an Omnidex Compiled Environment. | Use the following guide to determine whether to use an Omnidex XML Environment or an Omnidex Compiled Environment. | ||
| - | * Previous to version 5.0: use OACOMP to compile an Omnidex Environment Source into an Omnidex Compiled Environment and DBINSTAL to create and maintain Omnidex indexes. | + | * Previous to version 5.0, use OACOMP to compile an Omnidex Environment Source into an Omnidex Compiled Environment and DBINSTAL to create and maintain Omnidex indexes. |
| * After version 5.0 and before version 5.1, use OACOMP to translate an Omnidex Environment Source into an Omnidex XML Environment. This can be used with the CONNECT Statement or ODBC and JDBC connections. However, Omnidex XML Environments cannot be accessed by DBINSTAL so a shadow Omnidex Compiled Environment will have to be used for creating and maintaining indexes with DBINSTAL. | * After version 5.0 and before version 5.1, use OACOMP to translate an Omnidex Environment Source into an Omnidex XML Environment. This can be used with the CONNECT Statement or ODBC and JDBC connections. However, Omnidex XML Environments cannot be accessed by DBINSTAL so a shadow Omnidex Compiled Environment will have to be used for creating and maintaining indexes with DBINSTAL. | ||