Data Locks/Record Locks? Question

[Durien512]

I have a database that is used in a retail environment. I cant figure out what causes the locks of data.

I have an invoice (form) that it is filled out at point of sale(customer table). The middle section of the invoice (subform) gets the data from an inventory table.

The issue that i have is that often the subform locks up and does not allow the user to enter new data or make changes? It generally happens when they disconnect from the remote server, or loose connectivity???.

We use remote servers, using remote desktop connections.

The way i fix it is I take a backup database and move the tables out of the locked database into the new one. I just cant figure out what to do about this....>??


When you open an invoice at point of sale if the record is locked No line shows up on the subform to fill in. See image below.
When its fine the line will appear to take in entries.

 

[Durien512]

locked file shown..

 

[The_Doc_Man]

It generally happens when they disconnect from the remote server, or loose connectivity???.

If you lose connection to your database because of network issues, you are unable to consult the contents of the MDL file, which contains the locks. If that happens, you are automatically read-only.

There are other methods to lock yourself up, usually involving VBA recordset operations on the same recordset that drives one of the forms or subforms. You can also get caught if the recordset is open multiple times and two of the instances are trying to open the same record or the adjacent record. Access uses a buffer scheme such that if you try to allocate a chunk of its internal address space, you lock the buffer. If the other party tries to allocated another chunk and there is a potential overlap of the two buffers, the second party loses.

But from your description, I don't think the latter cases are significant. If you lose the network, it is time to go away and come back later. Or to look at a replication and synchronization process based on local copies and a replication master. (See Help Files for the latter topic.)