Search results

We do that for our other databases, where we have all the records ahead of time. This database receives records in real time and need to be operated on in a specific order.

Most of the time this isn't an issue, but as the day goes on the records available get smaller and smaller, but the team size doesn't change. This isn't something that can be changed, definitely not something I have any control over. Might look into this, the rules around record selection are...

The database only operates on a single record at a time, all queries operate on a single record at a time. The issue isn't with row-level locking on the table itself since that only applies for the duration that you are reading/writing data. The form uses a query that is effectively `select *...

The issue is that no built in locking is occurring which isn't really the fault of ODBC or Access. The data isn't stored in an Access DB, the Access DB we have is purely a front end to work on the data. MySQL will only lock the record when it is being actively queried, not when someone has it...

I've implemented #2, will see how it goes. If it doesn't work for whatever reason I will try #1 and report back. Thanks @sonic8 and @jdraw for your help Each user has a copy of the frontend DB on their local machine, they never use the "main" accde file.

We have already implemented the first part of that article, not quite the same but functionally similar 'Need to filter to the top record first and lock it DoCmd.OpenQuery "V3_Day1_OOH_Call1_select" 'log your name against the best unlocked record DoCmd.SetWarnings True 'Open script and now...

Hello, I have an Access Database that multiple people use at any given time, the database is split between a frontend and backend, the backend being an ODBC MySQL linked table (Not the traditional Access FE and Access BE). The issue I am facing is that since there are 3 or 4 people using it at...