>>>>>>When we tell our customers to use a UPS, they undersatnd that we are responsible and want to take care of our customers. Be aware that without a UPS you can never guarantee that your customers won't lose data. Make sure that your customers understand this!
>>>>>
>>>>>Of course, I agree with you.
>>>>>But this particular user makes backups regularly, and it has printed data so if anything goes wrong with table, user can easily restore database and insert missing data.
>>>>
>>>>So you tell them "nothing is lost - this is the black Friday for which you were diligently saving these copies... now where's the latest backup?".
>>>
>>>Something like that, yes, why?
>>
>>So you get their chestnuts out of the fire without burning your fingers, and not only come out as a smart guy who knew in advance what will happen, and you get a story to tell your other customers :).
>>
>>Beware - all happy tables are happy the same way, but each screwed up table is screwed up in its own and original way. Repair utilities handle the most common cases - knowing the hardware habits (buy cheap, but compensate that with low quality ;) back home, you may just be lucky to hit one of the original screwups. Just don't promise anything much, specially as there's no money there, just good relationships - try some magic, check whatever repair utilities you can dig up on the wiki, if some of them work, fine, if not, you tried - and they learned the value of a good backup and how futile it is to believe in miracles :), everybody happy.
>
>I am not sure what you're trying to say to me.
>I am aware of problems with corrupted tables but UPS's are not an option to my user that cost around 100 EURO's, and what else can I do except provide user with some repair utility?

Pedagogy. Most of them will never learn the value of backup until they have to redo the data entry for the last few months. The user in this case is the smart one, good for you - so even if the repair utility can't do a miracle and fix their table (and that was the other thing I wanted to say - there's always a chance that the first few dozen of kilobytes of your table are just binary trash, impossible to recover), they were smart and kept frequent backups.

Then calculate the time (and money in salary * hours plus losses because other work won't be done on time or at all) that would have been spent to reenter the data, and use this total to scare your other users into doing regular backups. That's the pedagogy I had in mind.