>>>>This message has been shown: Error: 2091 Table "name" has become corrupted. The table will need to be repaired before using again.
>>>>
>>>>Now, some probably had this error in past, so if anyone can tell me what to do, and how to prevent this happening in future, please help!
>>>>It's urgent!
>>>
>>>To prevent this from happening, you must make sure that your users don't turn off their computer withouit exiting your program. And make sure that all their computers have a UPS!
>>
>>Problem is in frequent power offs that user is having.
>>I don't know about UPS, I never suggest it, it's better to solve it programmaticaly.
>>That's why I asked for developers experiences, how did they solve that programmaticaly?
>>
>>One solution that I saw is SET TABLEVALIDATE, but I am not sure about that.
>
>You can NOT solve this programmatically, but you can reduce the problem which will also delay the program very much!! It's like when the brakes on your car don't work, you can fix them or drive very slowly...!
>
>Do yourself a favour and REQUIRE that your user have UPSes. In our contracts we require the use of one UPS per PC, or we charge them for the repair of the tables. First time 100$, second time 200$, third time 400$, fourth time 800$ and so on. And we also tell our users that we can never guarantee that all data will be recoverable. After a few bills the users buy a UPS....!

This is Serbia, if I tell my client to buy UPS I will get a smack in a head :)
I will not charge anything for repairing table, actually I have built small utility program that user can run by himself to repair table.