Multiple users 'pulling from queue table'

[Guest]

My application will have a table being inserted to via a web page.
The Access database will be in constant use by multiple users.
Periodically, users will need to pull items (read then delete) from the
queue in first-in first-out basis.
My concern is to avoid conflicts between pulling from the queue and records
being inserted via the web page (via ODBC connection) and also between
different users pulling from the queue simultaneously. I guess I need some
type of locking mechanism. Has anyone done anything similar?

 

[Ronald Dodge]

Have you looked at some of the ADO.NET stuff? Though I realize ADO.NET is
quite different in many respects from using ADO in Access, partly due to the
differences in the features, but also partly due to the fact you working
against a Jet Engine in Access. However, maybe you can take some of the
ideas from the ADO.NET and incorporate them into the Access project. That
is cause ADO.NET uses a disconnected database model, which makes the locking
situation much more tougher to deal with than it does with a continuous
connection to the database using a pessimistic locking mechanism. That is
because you are stuck with using an Optimistic locking mechanism and
therefore, you also have to deal with such things like transaction
submissions as to when to commit them and when not to commit them.

--

Sincerely,

Ronald R. Dodge, Jr.
Master MOUS 2000