|
Home > Archive > MS Access Multiuser > April 2005 > Record Locking in a Multi User Networked Environment - Still get same record
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Record Locking in a Multi User Networked Environment - Still get same record
|
|
| David N. via AccessMonster.com 2005-04-06, 8:06 pm |
| I have a database that is used by multiple users (30+) across a network.
Within this db, the user must select a field office code and a julian date
(both are numeric). Inside the tables is field that is like a control
number that contains the office code, the julian date, and a sequence
number. Once the user enters the data they click a button and it will
assign them the lowest control number based on sequence number where the
office code and julian date match. One problem: two or more operators are
able to assign themselves the same control number. Currently the way the
process works is that when it finds the lowest available control number
(one that has not already been assigned) it assigns it by opening the
table, entering the operators name and process date, saves it and closes
the table. I have already split the db into a front end and back end set
and I have tried the different record locking features of Access 2002. Any
ideals? I need to get this process fixed, and QUICK!
--
Message posted via http://www.accessmonster.com
| |
| david epsom dot com dot au 2005-04-06, 8:06 pm |
|
How To Implement Multiuser Custom Counters
DAO: http://support.microsoft.com/kb/q191253/
ADO: http://support.microsoft.com/kb/q240317
(david)
"David N. via AccessMonster.com" <forum@AccessMonster.com> wrote in message
news:5fec2b54197c4e2
28f93ac1f1180b95f@Ac
cessMonster.com...
>I have a database that is used by multiple users (30+) across a network.
> Within this db, the user must select a field office code and a julian date
> (both are numeric). Inside the tables is field that is like a control
> number that contains the office code, the julian date, and a sequence
> number. Once the user enters the data they click a button and it will
> assign them the lowest control number based on sequence number where the
> office code and julian date match. One problem: two or more operators are
> able to assign themselves the same control number. Currently the way the
> process works is that when it finds the lowest available control number
> (one that has not already been assigned) it assigns it by opening the
> table, entering the operators name and process date, saves it and closes
> the table. I have already split the db into a front end and back end set
> and I have tried the different record locking features of Access 2002.
> Any
> ideals? I need to get this process fixed, and QUICK!
>
> --
> Message posted via http://www.accessmonster.com
|
|
|
|
|