Q. Why can't I find my database in the list of ODBC sources?
A. In order for a data source to appear in the list, you must first have installed a driver for the particular database system and, then you must have configured the driver to point to your database.
Drivers are usually supplied by your database vendor, and, particularly if you are using a client-server database, you must make sure that you have installed proper components for your particular workstation and network.
A data source, in ODBC parlance, is a driver configured to point to a particular database. For instance, you might have a driver for Oracle data and two Oracle data sources, one for each of two clinical trials you are analyzing. You can configure an ODBC driver to connect to a particular database by running the ODBC driver manager from the Windows Control Panel. Only properly configured data sources will appear in Stat/Transfers lists of available data sources.
Q. I can see my data source on Stat/Transfer's list, but I encounter errors when I try to connect to it
A. There are many possible causes for this problem. Your ODBC driver may not be properly installed or configured for your network. Your database server and/or network may be down. You might not have proper access rights or the proper password for your database.
We suggest you try to connect to your database with another tool, particularly one that is supplied by your database vendor or a general tool such as Microsoft Excel. If you still encounter difficulties, you should first seek support from your local database administrator and/or the vendor who supplied your database or driver.
Q. I am having problems with ODBC or Access on 64 bit Windows. What should I do?
A. First, you should understand the somewhat confusing way by which Microsoft implemented ODBC on 64 bit Windows. There are actually two copies of the ODBC Administration Tool. The first, which is reachable from the Control Panel, can only create and modify 64 bit data sources. The second, which is identically named, but located in an obscure directory, creates and modifies data sources that use 32 bit drivers and which are accessible to 32 bit applications such as Stat/Transfer. You should only use the 32 bit Administration Tool, accessible from your Stat/Transfer program group, to create data sources for Stat/Transfer. Also, you must use the appropriate tool to edit existing data sources (See this Microsoft Knowledge Base article)
Second, the ODBC functions that are responsible for returning the names of data sources under 64 bit windows return both 32 and 64 bit data sources, even though 32 bit applications, such as Stat/Transfer. can only use 32 bit data sources. In order to avoid errors, Stat/Transfer only displays the data sources that it can use. Therefore, data sources that were created using the 64 bit administration tool are not visible from the Stat/Transfer menus.
Finally, if you create a data source and then cannot see it in Stat/Transfer, make sure that you have installed the 32 bit ODBC drivers. Some applications do not routinely install these on 64 bit machines, and, to make matters worse, the 32 bit Administration tool will blindly use 64 bit drivers.
Q. How can I join two tables in a relational database?
A. Many database systems allow you to define a "view", that will appear to Stat/Transfer as a single table. If you database allows this, it is the simplest and most robust way of joining tables for Stat/Transfer. If this option is not available, the Stat/Transfer command processor allows you to submit an SQL select statement. It is simply passed through to your ODBC driver, so it must be legal SQL for your particular database driver.