In Pervasive CC, what is your Communication Buffer Size, MKDE Buffer Size and Read Buffer Size set at?

OK, what about the Sort buffer Size under Memory Usage?

OK....then it isn't actually anything to do with buffers per se (red herring). Something to do with Novell 4 and how it is dealing with some of the newer TAS code that ISTS has incorporated into the latest versions and how that relates to Crystal.
 
I would try transfering your data to a secure location, and uninstalling Pervasive, DBA and Crystal from the server and the clients. Then re-install and try the Crystal report, but point it at the test database (99 company) and see if it works. If it does, bring your data back in from the secure location and try the report again.
 
If it blows up then you know that it is a data error.
 
If that is the case, you could try using the Pervasive utilities to attempt to isolate it.
 
Or you could try recreating the Crystal report from scratch and see if that solves the issue.
 
Other than that, don't know what else to suggest....
 
Except maybe try Access.....

I tried something new here.  I copied a 2000.1 version of workord.b to my 2002.4 (with updates) and the crystal report ran fine.  So something in the update rebuilding the files did not work correctly.  What programs can I run to rebuild the file.  I have tried the pervasive programs with no luck and I have tried all of the DBA programs, and the results are that everything is fine.

I have run update on the workord.b file several times.  The report opens in design view, but when you go to actually run the report and populate the fields, it blows up.  I have created new reports using workord.b and trying several combinations of fields in the report and it still blows up.  As soon as you try to access the data in workord.b you get the "data buffer length" error pop-up.
I have tried to use access in the past, but I have never had much luck setting up an odbc connection in Novell.

Scott,
 
I'm thinking that there is some piece of data that Crystal is trying to read that it is choking on. Which is why I was suggesting trying to see how Access would deal with the data. If Access is able to garb all the data and you can do one of the quick report formats (tabular or some such of the one-click type reports) then it is an issue with Version 7 likely choking on a data element from the latest structures in the Workord file. At that point you might look at seeing if a later version of Crystal has the same issue. Willing to bet it won't.....

I don't hink it is an issue with the structure...it is an issue with some data and how crystal "sees" that data....if Access has no problems though, you might consider using Access to connect to Workord and pull that into an Access table, and then connect the crystal report to the Access data source instead of directly to DBA.....