| Applies To: |
|
| Summary: |
| If the Citect compiler cannot open a file,
it will display the error message "Cannot Open File" giving the
file name of the file that cannot be opened. The most likely reason
for this error is either the file does not exist, you don't have
the correct rights to open it, or you have run out of file handles.
You can check if the file does exist with the file manager (check
with your network supervisor that you have correct rights to open
the file). If file does exist, and you have the required rights to
open it, then you have most likely run out of file handles. You
should increase the number of available file handles until the
error goes away.
You are more likely to run out of file handles if you have many include projects. When Citect compiles your project, it will open several files in each include project at the same time, so each extra project you include will increase the usage of file handles. If you get the "cannot open file" error message when you have added another include project, then you have run out of file handles. To verify that this is the problem, you could remove one of the include projects to see if Citect will then be able to compile your project. |
| Solution: |
| With Windows running on a network, the
setup of the number of file handles is in various places. To
increase the number of file handles in DOS, the setup is in the
CONFIG.SYS file. If you are using Novell Netware you must also
increase the file handles in the NET.CFG or SHELL.CFG file. You
must also increase the number used by Citect in the CITECT.INI
file. Set the following settings the the associated files:
CITECT.INI [CtEdit] CONFIG.SYS FILES=120 NET.CFG or SHELL.CFG file handles=120 There is also an upper limit for the dbfiles parameter of 196. If a value greater than 196 is enterend the behaviour of Citect will be unpredictable. If you have set the dbFiles to greater than 196 then set it back to 196. CIT has confirmed this to be a problem in Citect for Windows versions 1.0 to 3.0. This problem has been fixed in version 3.01. |
| Keywords: |
Related Links
Attachments