c=88 error when payroll is processed (almost everytime)

[vernalan]

Hey all, this is my first time to post, I've been reading earlier posts and I'm sure someone has some possible solutions for me to try. Thanks in advance!

Detailed Problem:
We are on a bi-monthly pay schedule. We enter time once a week for all employees. Out employees (approx 30) work in various states across the U.S., some are salaried with overtime, some are salaried without overtime, some are hourly. Almost everytime we process payroll the program crashes, we get a c=88 error and have to (if possible) rebuild the data or restore the data file with a back-up (which we create each time prior to processing payroll.)

System Specifics:

Program: Quickbooks Pro 2003 R8P

QB Server Machine: Dell dimension 4100 P3-933 Mhz/512 MB/W98se/20 GB hard drive. Just recently upgraded to the 512MB from 128 MB. Have only processed one payroll since this upgade. This machine shares a directory with the qb data file, otherwise it is used very little.

User 1: Laptop Dell Latitude CPXH500XT/P3-500Mhz/256 MB/W98se/18GB. This machine is theprimary user and usually is the machine where payroll is processed.

User 2: Dell Dimension 4100/P3-1000 Mhz/512MB/W2K/40 GB. Frequent User usually processing transactions in multi-user mode during payroll processing.

User 3: Dell Dimension 2400/P4-2400 Mhz/512MB/WXPsp2/80 GB/ Frequent User usually processing other transactions in multi-user mode during payroll processing.

Network: 100Mps Ethernet TCP/IP all users on same workgroup hub.

QB Data File: 95MP to 107 MB depending on how recently rebuilt. Condensed data Prior to '03 in July of '04. Size went from 132MB to 84MB. Audit trail enabled.

What I am Looking For:
1. What can I do to increase reliability and reduce program crashes.

2. Has anyone else experienced frequent payroll processing related c=88 errors and what did you try?

3. System optimization theories and practice that we could benefit from.

4. Idealy a solution to this problem without having to drop to single user mode , thus keeping everyone working.

What I have tried:

A. Increased RAM in QB server to 512 MB

B. Removed NAV 2000 from QB server - increased performance dramatically.

I look forward to your responses.

Vern

[tallman]

This error is usually caused by the data file not being closed correctly by windows or a windows resource issue on the PC that first gets the error. Since the PC getting the error is Win-98 and the server; (1) try doing payroll on a differant PC to see if you get the error (2) do full shut-down on that PC. I have found that Win-98 may not free all of the resources a program was using when it is closed. Shut-down is the only way to force Windows to clear that memory.