AppxODBC connects to the APS/ADC over a TCP/IP link, including access over the Internet. Before continuing, please verify that you can access the Presentation Server or APPX Desktop Client from a client PC on your network, using the same server user ID and password you plan to use for your AppxODBC connection. This is a good way to verify that you're not running into any issues with spelling or upper/lower case of your user ID and password (in addition to security or OS issues most commonly seen if you are trying to access data on a Windows, rather than UNIX, server).
You can verify this by telnet'ing into the server (in the case of a UNIX machine) or ping'ing the server, from the client.
If the PC on which you're installing AppxODBC has a prior release OR BETA version of AppxODBC on it, you must do this step for the installation to work correctly.
(If you are installing AppxODBC on a machine for the first time, you can skip this step, as there are no old version DLL's to remove.)
If the following two files exist, please delete them from your Windows\System directory:
Run 'APPXODBC.EXE', the AppxODBC installation program.
A new ODBC data source named 'appxodbc' will be automatically defined. You can use this data source with third-party ODBC clients such as Excel and Crystal Reports. Note: The APPX ODBC directory will be written to by the ASQL import function. Please install APPX ODBC into a directory with WRITE access, such as C:\APPX\APPXODBC\
Run the "asql" program in your installation directory, and specify which APPX files you want the PC user to be able to access via ODBC:
C:\APPXODBC> asql
or from the shortcut created on your desktop
'asql' imports APPX data dictionary definitions into the AppxODBC relational dictionary. It will read the APPX SYSDIR (system directory) file available at the server/port specified, and allow you to select those files you want to reveal through ODBC.
Once you have selected the files you want, press the "Import Definitions" button - 'asql' will read the APPX data dictionary, produce SQL 'create table' scripts for each file you selected, and run those scripts for you automatically, behind-the-scenes.
Limiting access to the "asql" program, and only specifying a subset of the APPX files as available via ODBC may be useful to you as a security measure, to protect your application from well-meaning but curious users equipped with various PC programs that can read and modify data via ODBC.