Thanks Craig. Tripling support fees sounds like most effective with commercial customers. Mine are colleges and they don't even want to pay normal rate for fixing their data. Some are not "computer-aware" and if someone unplugs the computer while the software is running and the it stops working, they believe it's a flaw in the software that must be fixed at developer's expense.

Data buffering / transactions sound like the way to go for this one.

Mon

>A number of things come to mind:
>
>- You can put a timer in your program that will close the app after x minutes of inactivity.
>- Charge your customer your normal rates the first time to fix the problem, but tell them next time it will cost 3-4 times your normal rate. Management usually gets the idea after the first call at the increased rate.
>- Use data buffering.
>