It is when you try to print that causes the error? At what point does the problem occur (does the report begin to compile, select records, start to print to paper, etc)?

Do you have any other modules that use the Crystal Print Engine (such as Accpac for Windows)? There are a couple known issues with ufl files in the \winnt\crystal directory. The specifics are on another post (April 1/1999) in this forum.

Do you have a selection formula for these reports? If so, please remove it and try again. If not (or even if so), try to restrict the data even further (ie just for month to date or something like that).

Which modules are these large reports based on (AR, GL, etc)?

I assume when you say 'scanning thru IC database', that means you are previewing or printing the report. If you haven't already, could you test restricting the data that is selected for the report? One way to do this is to put into the record selection formula something like: Item Number = 'xxxxxx', where you fill in a specific item number code for the x's.

I have had one report some time ago that problems occured with a huge database (about a Gb of data), and that restricting the data allowed the report to print. Obviously this isn't a solution, but I want to find out if this is part of the problem.

Also, if you have room on your local hard drive, could you make a copy of your data and try printing the report locally (if in fact you have data on a network)? This would eliminate any network environment considerations as to the problem you are having.