Microsoft KB Archive/127841

{|
 * width="100%"|

-

The information in this article applies to:


 * Microsoft FoxPro for Windows, versions 2.5x, 2.6x

-

SYMPTOMS
After you use the REPLACE or UPDATE commands in a multiuser environment, the modified records are not written back to the .DBF file correctly.

RESOLUTION
Perform one of the following to work around this problem:


 * Use the FLUSH command immediately after the REPLACE or UPDATE command to write all buffers to the .DBF file.

-or-
 * Keep a BROWSE window open at all times on one of computers that has the multiuser table open. A BROWSE window kept open all the time causes FoxPro to write back its buffers after the interval set by the SET REFRESH command.

-or-
 * Use the REPLACE ALL command only when a .DBF file is opened in exclusive mode.

STATUS
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem was corrected in Visual FoxPro 3.0 for Windows.

MORE INFORMATION
NOTE: This problem does not occur in FoxPro for MS-DOS.

Steps to Reproduce Problem
CAUTION: Performing these steps changes all records of the CUSTOMER.DBF table located in the TUTORIAL subdirectory.

 Start two instances of FoxPro on the same or different computers. If both instances are on the same computer, arrange the screen so you can see both instances at the same time.  In the first instance, type the following in the Command window:    SET EXCLUSIVE OFF SET REFRESH TO 1,1 USE SYS(2004)+"\Tutorial\Customer" BROWSE   In second instance, type the following in the Command window, but do not perform a BROWSE.    SET EXCLUSIVE OFF SET REFRESH TO 1,1 USE SYS(2004)+"\Tutorial\Customer" REPLACE ALL contact WITH "Test" 

Notice that only the first record in the BROWSE window of the first instance has changed. Additional query words: Fixlist3.00 vFoxwin 2.50 2.50a 2.50b 2.60 2.60a FoxWin buglist2.50 buglist2.50a buglist2.50b buglist2.60 buglist2.60a

Keywords         : FxprgMultiuser Version          : 2.50 2.50a 2.50b 2.60 2.60a Platform         : WINDOWS Issue type       :
 * }