This shows you the differences between two versions of the page.
|
dev:home [2009/12/04 01:34] tdo |
dev:home [2016/06/28 22:38] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
| - | ====== Omnidex Development ====== | ||
| - | Omnidex Development uses the following main components of the Omnidex Software. | ||
| - | |||
| - | * Omnidex Administrator | ||
| - | * OdxSQL | ||
| - | * OdxNet | ||
| - | * OdxAim | ||
| - | * Omnidex ODBC Driver | ||
| - | * Omnidex JDBC Driver | ||
| - | * RDBMS Stored Procedures | ||
| - | |||
| - | Omnidex Development primarily takes the form of developing either an ODBC or JDBC based application or using either SQL Server or Oracle Stored Procedures. | ||
| - | |||
| - | Applications have also been previously developed using the OmniAccess API (OA) and Client OmniAccess (CLOA) api. DISC recommends that all future Omnidex development use ODBC, JDBC or the Stored Procedure Interface. | ||
| - | |||
| - | * [[odbc:home | ODBC ]] | ||
| - | * [[jdbc:home | JDBC ]] | ||
| - | * [[stored_procedures:home | Stored Procedure Interface ]] | ||
| - | |||
| - | Applications using Omnidex have been developed using: | ||
| - | |||
| - | * C | ||
| - | * C++ | ||
| - | * C# | ||
| - | * PHP | ||
| - | * Java | ||
| - | * Cold Fusion | ||
| - | * Microsoft Access | ||
| - | * Microsoft Excel | ||
| - | * MicroStrategy | ||
| - | * Oracle Business Intelligence | ||
| - | * SAP Business Objects | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||