I would try to find out why. You are trying to eliminate the consequences of a serious problem, I would try to fix the problem instead. Are other applications involved? If not, it sounds like a problem with dangling references.

>Its a machine who receives signals from an external device. It usually HAS to reboot, don't ask me why :)
>>As Sergey pointed out, close the table immediately after the insert.
>>
>>However, if the machine is frequently rebooted or has the power shut off, I would found other clients to work for.
>>
>>NB! What about using a UPS?
>>
>>>Thats what I'm using, but it keeps getting corrupted
>>>>I prefer to use the SQL Insert command instead. I have found it to be much safer compared to the old fashioned Use-Append blank-Replace way.
>>>>
>>>>>I tought about that, and Ill do that change. I hope that don't add much to execution times. Thanks
>>>>>>To minimize possibility of corruption, don't keep the table open all the time: Open table, Add record(s), Close.
>>>>>>
>>>>>>>I'm using a small, quick and dirty prg to do some data transforming and I have a small function call log wich simply adds an event to a dbf log table . The production machine is often rebooted or the power is cut (that can't be changed). When that happens, the log dbf becomes corrupt (it is always opened during the program execution and the program is designed to run all the time).
>>>>>>>Is there a way to ensure that the DBF not become corrupt after a reboot or system hang?
>>>>>>>
>>>>>>>TIA