>>>>>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.
>>>>
>>>>Most of users realize that (my users, that is to say). Those that don't, well that's their problem if they were warned of regular backups, in which they are in my case. I really don't have patience and need to scare users to do backups. I just say, "your data, your problem".
>>>
>>>I should have trademarked that... the official general instruction sheet, the stuff common to all our apps, ended with, literally: "programi naši, podaci vaši, svako cuva svoje stvari" :) (ours the code, yours the data, everyone takes care of their own things).
>>
>>LOL, maybe it's our Serbian mentality (srpska posla), but I really mean that.
>
>So did I - that sheet was an official document. I think it was even on our website :).

I couldn't agree more with that sheet. :)

But, let me just say, even though my user had that problem with corrupted data, I didn't want to leave him with sentence "I told you that you should've buy UPS, or I told you should've make regular backups". One member here told me that I should've charge him for repairing table. I didn't want to charge anything and I didn't want to act like some smart ass. People is depending on that program for living, and I know that capitalism demand that I take as much money I can for that, but it wasn't really theirs blame, even if they didn't listen, it's somewhat specific case that I can't go in detail here.