Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
QUIT COMMAND
Message
From
21/03/1997 19:53:31
Mike Yearwood
Toronto, Ontario, Canada
 
 
To
21/03/1997 18:08:55
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Title:
Miscellaneous
Thread ID:
00025254
Message ID:
00025262
Views:
26
>I read about the QUIT command, from
>the text it look like I I have to use this command in my code otherwise your databases could be corrupted?
>
>Is this a fact or?
>
>Best regard
>
>Per Simmersholm

No command can prevent database corruption. As long as data has been written and still exists in a buffer somewhere (Foxpro has its own buffers, your workstation has buffers and the server has buffers), partial data can be written to the drive causing data corruption. FLUSH flushes Fox's buffers, but doesn't affect the workstation's or the servers buffers. Closing and opening the tables doesn't help. This just slows things down, so you can stop doing that. VFP has a scheme for minimizing data corruption. It isn't fool proof either. The only bullet proof mechanism would be one where the workstation writes a record to a temporary table and closes the table. A copy of VFP running on a UPS protected machine could then read these temp files from each workstations and commit them to the actual table. This is a primitive example of the kinds of thinkgs to make client/server apps so popular.

Mike
Previous
Reply
Map
View

Click here to load this message in the networking platform