If the server function requires parameters (called input host variables), these can be supplied by placing parameter markers in the syntax (indicated with a ‘?’) and then specifying the parameters as the second and subsequent arguments to $ServerFunction. Here is an example: change all orders where orderno = 1003 \ let RequiredByDate = $ServerFunc(‘trunc( ?,…
Read more
Adding More Power and Flexibility to Zim Zim is a powerful and flexible environment for developing and using all types of database applications. Zim‘s Entity-Relationship (ER) data model and fully-integrated Object Dictionary enable progressive program development, whether the information processing system is simple or complex. Zim Server provides a database server capability that can be…
Read more
The various XML technologies incorporated into ZimWeb may require references from one source to another (e.g. one XSLT stylesheet referencing another, or a reference to an external image in XSL-FO). The following explains precisely how references to other sources (URIs) are interpreted in different circumstances. URIs in XML generated by the Zim database agent…
Read more
Errors generated during the Zim Server Connectivity activity can be checked via the system variables $SQLErrCode and $SQLErrMsg. The first one contains the error number and the second one the message text corresponding to that error number.
The Zim “COMPILE” command is capable of compiling application programs in one of the same three modes as described for program execution: SQLMODE SQL mode SERVERMODE Zim Integrated Server mode ZIMMODE Standard Zim mode The default mode of operation is SERVERMODE. For all database servers except Zim Integrated Server, SERVERMODE and SQLMODE behave identically. In…
Read more
When developing client-server database applications, it is important to consider the location of the data. Any data under the control of the database server contributes to both the load on the network as well as load on the server machine. Because of this, it is important to analyze the data associated with a given application…
Read more
In Client-Server applications, you do not have to do anything special to access or manipulate data stored in the SQL database. The data definitions of objects under Zim’s control and the data definitions of objects not under Zim’s control are exactly the same. To an application, Zim manipulates both in exactly the same way. The…
Read more
Zim supports two types of transactions: implicit and explicit. An implicit transaction is associated with each individual Zim command that accesses the database in some manner (either read/only or read/write). When the command ends, all locks that were acquired are released and any database updates are committed to the database. If the command fails (e.g.…
Read more
If the Zim application being developed is based on an existing SQL database, then the Zim definition interface needs to be executed in order to import the definitions of the relevant tables from the SQL server and populate the Zim data dictionary so that the application can be developed. Conversely, if the Zim application has…
Read more
English 
Portuguese