-
SQL Database Servers Connectivity
-
- Migrating Applications to Client-Server
- Configuring the Date Mapping for SAMs
- Defining Numeric Fields with Decimals
- Defining Tables in Zim
- Indexing Virtual Fields
- Flagging Objects for the SQL Server
- SQL Views
- SQL Table Subsets
- Uniquely Identifying the Compiled Application
- SQL Table "Owners"
- Naming Differences between Zim and SQL
- Caveats
-
ODBC Driver Connectivity
-
Zim Integrated Server (ZIS)
-
ZIM and DDE Services
-
ZimWeb
Zim on Windows
Print
< All Topics
Zim Client-Server uses the SQLCPI variable to find the SAM module and the utilities used to import and export objects. Under Windows, the SQLCPI variable is set in the Windows registry and is set to the directory where the SAM software is installed.
When running Zim on Windows, ensure that the registry variable SQLCPI is set properly.
Verify that the SQLCPI registry variable has been set properly from within Zim by outputting the $SQLPath system variable, as shown below:
> output $SQLPath
c:Zim
Was this article helpful?
0 out Of 5 Stars
| 5 Stars | 0% | |
| 4 Stars | 0% | |
| 3 Stars | 0% | |
| 2 Stars | 0% | |
| 1 Stars | 0% |
Table of Contents