Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Slow save in VFP9 comparing with VFP8
Message
From
26/05/2005 14:47:41
 
 
To
24/05/2005 16:25:58
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01015381
Message ID:
01017922
Views:
24
This message has been marked as the solution to the initial question of the thread.
After talking with Microsoft I resolved the problem with slow save. After the transaction is committed, the business object uses the FLUSH command to save the data to disk. MM uses the command FLUSH FORCE, which is only partly supported in 8.0. The FORCE part of the command was never implemented in 8.0, which forces the data to disk immediately. Because of this, the operating system flushes the files when it deems necessary. Issuing the same command in 9.0 forces all the open files to flush immediately. In 9.0, you can control which file you want to flush by issuing the correct parameter--FLUSH IN &lcAlias FORCE.

The command works in both versions because anything following the FLUSH command is ignored in 8.0. Obviously it’s preferable to flush the file immediately after the transaction is committed, but only if the file being acted upon is flushed and not every open file.

            IF THIS.lUseTransactions AND NOT llRollBack AND NOT llIsRemote
                        loExecutant.EndTransaction()
                        *sys(1104) && Make sure the changes are written on the disk
                        LOCAL lcAlias
                        lcAlias = This.Getalias()
                        FLUSH IN &lcAlias force 
            ENDIF
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform