ACC: Locks Go Away on Forms Based on MS FoxPro v. 2.6 Table

ID: Q154905

The information in this article applies to:

SYMPTOMS

Novice: Requires knowledge of the user interface on single-user computers.

The record locks for a form based on a linked Microsoft FoxPro table are released after a period of time. When this happens, multiple users can update the same record even though the RecordLocks property of the form is set to Edited Record.


STATUS

Microsoft has confirmed this to be a problem in Microsoft Access 2.0 and 7.0. This problem no longer occurs in Microsoft Access 97.


MORE INFORMATION

This behavior does not occur at the table level or if the form is open in Datasheet view.

Steps to Reproduce Problem

In Microsoft Access 7.0


  1. Open the sample database Northwind.mdb. Do not open it Exclusive.


  2. Select the Customers table.


  3. On the File menu, click Save As/Export.


  4. Click to select "To an external File or Database," and then click OK.


  5. In the Save Table dialog box, select Microsoft FoxPro 2.6 from the Save As Type list, and then click Export.


  6. On the File menu, point to Get External Data, and then click Link Tables.


  7. In the Link dialog box, select Microsoft FoxPro from the Files Of Type list. Select Customer.dbf, and then click Link.


  8. In the Select Index Files dialog box, click Cancel. Click OK when you receive a message that the table is attached, and then click Close in the Link dialog box.


  9. Select the attached FoxPro table Customer1. On the Insert menu, click AutoForm to create a new form based on that table.


  10. Open the form in Design view. On the View menu, click Properties.


  11. Change the form's RecordLocks property to Edited Record. Save the form and close it.


  12. Open the form in Form view and type a letter in the first field.


  13. Start another instance of Microsoft Access 7.0 and open Northwind.mdb.


  14. Open the form you created in step 9 and try to type a letter in the first field. Notice the lock symbol that appears in the record selector.


  15. Leave both forms open for about 5 minutes. At some point the record lock symbol will disappear from the second form, and you will be able to edit the same record on both forms.


In Microsoft Access 2.0


  1. Open the sample database NWIND.MDB. Do not open it Exclusive.


  2. Select the Customers table.


  3. On the File menu, click Export.


  4. Select FoxPro 2.6 in the Export dialog box, and then click OK.


  5. Select Customers in the Select Microsoft Access Object dialog box, and then click OK.


  6. Note the file name and directory in the Export To File dialog box, and then click OK.


  7. On the File menu, click Attach Table.


  8. Select FoxPro 2.6 in the Attach dialog box, and then click OK.


  9. In the Select File dialog box, select the Customer.dbf file, and then click Attach.


  10. In the Select Index Files dialog box, click Close. Click OK when you get a message that the table is attached, and then click Close in the Select File dialog box.


  11. Use the Form Wizard to create an AutoForm based on the attached Customer table.


  12. Open the form in Design view. On the View menu, click Properties.


  13. Change the form's RecordLocks property to Edited Record. Save the form and close it.


  14. Open the form in Form view and type a letter in the first field.


  15. Start another instance of Microsoft Access 2.0 and open NWIND.MDB.


  16. Open the form you created in step 11 and try to type a letter in the first field. Notice the lock symbol that appears in the record selector.


  17. Leave both forms open for about 5 minutes. At some point try to type a letter in the first field again. The record lock symbol will disappear from the second form, and you will be able to edit the same record on both forms.



REFERENCES

For more information about record locking, search for "record locking," and then "Editing data in a multi-user environment," using the Microsoft Access 7.0 Help Index.

Additional query words: lock FoxPro 


Keywords          : kbinterop IsmXbase 
Version           : 2.0 7.0
Platform          : WINDOWS 
Issue type        : kbbug

Last Reviewed: April 30, 1999