Category: ZIM:X Connectivity

The Original Internet Language

Guidelines to Use Zim Server Connectivity

There are two different moments when dealing with Zim Server Connectivity: 1) The preparation of client database: this step is done only once and creates data definitions to allow the client database to “see” what is defined in the other Zim database and it is obligatory; 2) The preparation of remote database: the other database…
Read more

DDE Error Return Codes

The return value of $DDEFunction is one of the following. A negative result indicates failure. Value Description 0 DDE service completed successfully. -1001 Bad DDE service indicator type; p2 is not of type longint or int. -1002 Unknown DDE service indicator value; p2 not 1, 2, 3, 4, or 5. -1003 Attempt to CONNECT failed.…
Read more

Zim Integrated Server (ZIS)

Windows Zim Server can be started manually from the Start menu, or the Startup folder. You can also start the process from the command prompt:   start zsvserv.exe [-p <port number> | -s <service>]   This command starts Zim Server in its own console window. The -p option sets the port number on which the server is listening. The -s option does the…
Read more

Exporting Zim Table Definitions

If you have developed an application in Zim and want to maintain a portion of the data in an SQL database, the definitions of those objects must be maintained in the SQL database as well as in Zim. Zim’s SQL definition interface translates Zim definitions into equivalent definitions in the SQL server environment. Refer to…
Read more

Importing SQL Table Definitions

If you are developing a Zim application to run against an existing SQL database, you must create an equivalent representation of that data in Zim. Zim’s definition interface translates SQL definitions into equivalent definitions in Zim. The mapping of SQL tables to Zim EntitySets or data relationships is straight-forward. A Zim developer must first establish…
Read more

Security Considerations

Because client and server are separate processes (and can even be on different machines) with Zim Server Connectivity, there are some new options for providing security, although the same basic mechanisms are used. Using ZIM Security Within Zim, security is provided through a combination of log in user names, passwords, and entity set, relationship, and…
Read more

Controlling Program Execution

Zim application programs can be compiled in ZIMMODE, SERVERMODE, or SQLMODE depending the type of the data dictionary objects used (fields EntType, RelType or DocType). See details in the Zim command SET COMPILEMODE. Zim applications can operate in ZIMMODE, SERVERMODE, or SQLMODE by means of the use of the command  SET EXECUTEMODE which controls the…
Read more

Connecting to SQL Database Servers

All SQL servers require that some type of connection be established between a client program and the server before any database operations can be attempted. In Zim, a connection between a Zim application and an SQL server is established by the “CONNECT” command and removed by the “DISCONNECT” command. During the execution of any Zim…
Read more

Tracing Zim Server Connectivity

There are two ways of tracing the activity of the Zim Server Connectivity: 1) At the client side: when accessing a remote database, Zim translates Zim commands syntax into an appropriate syntax for execution on the remote server. In general, Zim commands are executed through a combination of processing at the server (or at several…
Read more

Performance

The use of Zim Server Connectivity in an application has an impact on performance. There are several factors to consider: Client-server configurations introduce additional overhead that is not present when an application is using a local database. The most obvious overhead is that every database request must be translated into a server request, the request…
Read more

en_CAEnglish