I am getting a "533 error - could not open database" while using Adagio Receivables and printing reports, namely an ATB or Over Due Receviables listing. Statements print fine.

I have searched both the pluscommunity and the Softrak BB database and only found one
reference for a Quik Check problem posted in Jul/99.

I have checked all of the settings and suggestions from that posting and I still have the problem.

I even went so far as to strip down the folders so only the minimal required subdirectories were accessible (\arasp \asp \softrak etc.), and I still get the error. I have even tried running from a very basic Win95 machine with no chance of having any type of Crystal files installed previously.

This is running on a Novell network, has over 2000 customers and probably 5,000+ transactions.

Any insights appreciated.

Dear MLS,

The error message 'Error 533' is a fairly generic 'catch-all' message, similar to the Windows error 'this program has performed an illegal operation'. Error 533 could be related to a number of different reasons.

The usual reason for this error has to do with the Crystal Files (as you mentioned), and often simply re-installing the program will fix the problem. If you have Adagio Receivables on the network (programs and data), can another workstation print these reports? If so, then some files on your local station (ie Crystal files, crpe.dll, etc) are not up to date, and you should re-run the workstation setup (wksetup.exe) with full Supervisory rights.

Also, if you have 'orphan' batch files (ie data files that don't belong but exist due to an improper data restore), this error can appear. Try printing the same reports on Sample data (\softrak\crwin\samdata), If they work OK, then something in your data is preventing the reports from working.

Because Receivables currently uses a Crystal 4.0 engine for printing reports (this will change in the next release), there could be problems with printing large data sets. Can you print the report for a single customer? A range of 50-100 customers?

Regards,

When the problem first occured, I reinstalled Receivables and got the same results. I also went to different machines that were not running the program and installed the workstation version there and still the same results. At this time, any machine on the network that tries to print these reports gets the same results.

I have also tried to limit the range to the smallest account set (there are 12 in total) and I still get the error.

I will have to try the sample data to see what happens then, but I am interested in what I might look for in the case where you say there may be files that do not belong. I know the data has been restored and the old files would have been renamed rather than loading on top of the old data, so I'm not sure what else it could be in relation to the restoring data.

I will let you know what happens with sample data, in the mean time I hope the additional information is helpful to you.