Hi:
We distribute a program that uses the RDC (CR version 8.5) to create a CR object. We sell thousands of copies of the software each year.
We have a few customers who report an error "Error opening file File could not be found, crheader.dbf at file location
c:\adm\userdb\-11\crheader.dbf." This is a FoxPro 2.6 table that we connect to for the report, and is the first table accessed by the report. Invariably, the file is in the specified location, and is not read-only. Users have appropriate security rights to the folder.
The customers who report this have a variety of OS & network configurations, some XP, some NT, some W98.
We cannot re-create the symptoms on our test rack. The one and only time we were able to fix this was with a re-install of our software.
Any ideas as to what's going on? We've suspected corrupt install files, perhaps some obscure MS security issues, incorrect dll's, just about anything we could think of. The code works for 99.99% of our users.
Just a clarification - intermittent refers to the number of customers. When this happens to a customer it happens all the time, with each of the 34 reports we distribute. All reports are compiled with database location same as report.
TIA,
Dan
Dan Walter
Daniel.Walter@uvm.edu
We distribute a program that uses the RDC (CR version 8.5) to create a CR object. We sell thousands of copies of the software each year.
We have a few customers who report an error "Error opening file File could not be found, crheader.dbf at file location
c:\adm\userdb\-11\crheader.dbf." This is a FoxPro 2.6 table that we connect to for the report, and is the first table accessed by the report. Invariably, the file is in the specified location, and is not read-only. Users have appropriate security rights to the folder.
The customers who report this have a variety of OS & network configurations, some XP, some NT, some W98.
We cannot re-create the symptoms on our test rack. The one and only time we were able to fix this was with a re-install of our software.
Any ideas as to what's going on? We've suspected corrupt install files, perhaps some obscure MS security issues, incorrect dll's, just about anything we could think of. The code works for 99.99% of our users.
Just a clarification - intermittent refers to the number of customers. When this happens to a customer it happens all the time, with each of the 34 reports we distribute. All reports are compiled with database location same as report.
TIA,
Dan
Dan Walter
Daniel.Walter@uvm.edu