Applies To:
  • CitectSCADA 1.00 1.01 1.10 1.11 1.20 2.00 2.01
Summary:
If you compile your database on one computer and then try to run that database on another computer with different drive mapping's, Citect will not be able to find files in the include databases. This will show up with the error "Cannot Display Page". This will be displayed when you try to display a page via the function PageDisplay() and this page is in one of the include databases.

When Citect compiles your database it creates a list of the include database paths. This list will then allow Citect runtime to find any files in your include databases directories. If however you compile your database on one computer and then run the database on another computer with different drive mapping's the list of paths will be incorrect. So Citect will not be able to find any files in your include databases.

This will occur if you have a file server (Novell Netware, LAN Manager, Windows NT etc) and the drive mapping on the compiling Citect is drive F:\ and on the running Citects it is drive E:\. This is more likely to occur if you are using Windows for Workgroups to be a File Server and you are using the Windows for Workgroups file server as a Citect node. With this configuration the Citect on the Windows for Workgroups file server will see the databases on drive C: while all the other Citect will see the database on drive E:\.

 

Solution:
To solve this problem you should make the drive mapping's the same for all computers. If you are using Windows for Workgroups you may do this by using the DOS SUBST command to make extra drive letters. Then use the same driver letter to compile and run Citect on all computers.

In version 2.10 and later Citect will check if the path to the RUN directory is the same as the compiled list. If the paths are different then Citect will assume that you have compiled the databases with a different drive mapping's. When this is the case Citect will then substitute all the drives mapping's in the compiled list to the same as the RUN directory. So upgrading to version 2.10 or later will solve this problem.

The automatic substitution introduced in version 2.10 and later may cause problems if some of your include databases are one different drive letters or sub directories as, Citect will make them all the same as the RUN directory. You may stop this substitution from occurring by setting the parameter [CtEdit]RunSubst=0.

Another solution is not to have any include databases or to copy the compiled pages in any include database into the RUN database. To do this you must copy all the *.RDB *.CTG, *.CTL and *.CTT from your include databases into the RUN database. You should only do this if you cannot solve this problem any other way as it will cause you a maintenance problem, because you must re-copy the files whenever you recompile your database.

 
Keywords:
 

Attachments