Help still waiting for an answer ASAP please

[MrHelpMe]

Hello,

Still waiting on an answer for Cannot open Control file after compiling report. I have done what crystal recommends with the read only check mar however, this was unsuccessful at solving the problem. I am using windows NT and have never had this problem before. Any ideas why I am getting this error and what is the fix for it. Thanks.
p.s. If your wondering, I do have the .exe, .cfr and .rpt file in the same location. Your help is appreciated.

 

[sp1060]

I have had this happen often. "Cannot open Control file" is due to a problem with the CRF file. In my case, the reports often reside on more than one server and I can simply replace the crf file with one from another server. I'm not sure why these files get corrupt, but they do. If you cannot copy the crf file from somewhere else, I think you will need to re-compile.

 

[sjonesnottinn]

I had a similar problem and found the solution as follows:

I creaded and ocmpiled the report on a machine that had the database set up through ODBC as User DSN as opposed to System DSN. I installed the report on anothe workstation and would get the cannot open control file error. That workstation had the database set up through ODBC as System DSN. I reconfigured my machine to System DSN, recompiled and distributed the report. Renistalled report on workstation and it worked.

 

[nds]

I just experienced the "Cannot open control file" error when launching a compiled Crystal report. I had been locking down security on the shared folder in which the compiled report resides. I restricted my users to "Read & Execute", "List Folder Contents", and "Read". Apparently, every time a compiled report is run the CRF file for the report is modified, so I had to add the "Modify" permission for my users.

I had tested launching these reports right after I had restricted user permissions on this folder, by logging on with a userid with no special permissions, and it worked. Later that day I got a call reporting the error. I think the error is experienced by the *second* user that tries to launch the compiled report and does not have the "Modify" permission on the CRF file.