Craig,
Thanks for the tip on the Novell Drivers. I'll take a look on their site.
The problem only occours a few times a month across all customers so it is not a real big deal but when it happens it looks like a bug in our program. Becuase of the volume of data these shops process, restoring from backup just because one repair order or invoice is out by a few dollars is out of the question. It might be 3 or 4 days before the problem is found. We just call in with PC Anywhere and fix it manually. Because of the tight margins in the Auto Body repair business we would have a lot fewer customers if we told them they all had to replace their junk with name brand approved PCs. For us it is a tradeoff between the hassle of dealing with the junk and making sales and getting the annual support contracts. I am looking for a way to "tighen up" what we have so if there is a problem we can say PC xyz sent bad data again and it was rejected. Right now I can't do that.

John.


>Actually, you can have control over the hardware. First, you can make the make the minimum hardware requirements for the application much stricter. Second, if you provide database recovery for your customers, charge them more money for it. I typically charge three times my standard hourly rate. It usually only takes one time to convince the customer to make changes to their systems.
>
>There are known issues with some Novell drivers and FoxPro. The problem is with the driver. There are several KB articles on the Novell web site that discuss this.
>