I surrendered and installed Personal MSSQL. Everything is working well now. But about the machine rebooting, this is a requirement in some kind of OLT systems, like ATM's. They should be able to maintain database integrity on almost every event (but I have seem a fair share of Oracle and MSSQl servers corrupted by a power failure).
>>>>>Hello.
>>>>>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
>>>>
>>>>After reading some of this thread it makes me think you need some way to close the VFP app when the machine is rebooted.
>>>>
>>>>You might want to make a little .NET app that can signal your VFP app when the machine is shutting down, and let your VFP app close itself. You could also make a wrapper of the .NET class the following article talks about and use it directly in your app.
>>>>
>>>>See..
>>>>
>>>>http://blogs.msdn.com/b/jaredpar/archive/2006/10/20/responding-to-windows-shutdown.aspx
>>>
>>>No shutdown events are fired if the machine is simply turned off, or if someone hits the Reset button.
>>
>>Yes. If that is how someone regularly shuts down a windows machine, he/she needs to find another line of work.
>
>Exactly. Or as I wrote in another message, find other clients to work for.