Adding records concurrently

#1 (**permalink**) 28-Jul-2006, 08:30 AM

I've inherited a database that is being used to store customer information.
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/information-technology/12625-adding-records-concurrently.html
We need to keep a log of customers no longer with us, with no activity in
several years.
Windows XP, Access 2003.
Several users are adding records at the same time, and once in a while,
different users get locked out of the system!
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=12625
The key is ID, Autonumber, Indexed=yes, no duplicates. I have open
mode=shared, locking=edited record, and record-level locking set. What else
should I be looking at?
Thanks in advance!

*

#2 (**permalink**) 28-Jul-2006, 08:30 AM

Ned Fraser wrote:
> I've inherited a database that is being used to store customer
> information. We need to keep a log of customers no longer with us,
> with no activity in several years.
> Windows XP, Access 2003.
> Several users are adding records at the same time, and once in a
> while, different users get locked out of the system!
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=12625
> The key is ID, Autonumber, Indexed=yes, no duplicates. I have open
> mode=shared, locking=edited record, and record-level locking set.
> What else should I be looking at?
> Thanks in advance!
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=12625

It is normal when more than one user is accessing and editing data in
Access for one or more to receive an error message. Since it is possible
that they may be editing the same record and by the time the second one is
making a change the first one may have made a different change that the
second one is unaware of and should know about before committing their
change.

It can be irritating at times. I might also suggest that in some
versions of Access it is possible that they may not have even been working
on the same "record." If it happens a lot there are procedures that may
help, depending on the work flow of the office.

If by being locked out you mean something different, sorry I can't help,
that never happened to any of my applications.

--
Joseph Meehan

Dia duit

#3 (**permalink**) 28-Jul-2006, 08:30 AM

The users are only adding, not editing records. The records being added are
never duplicates (the users are adding records based upon separate paper
files), and the key is an autonumber ID, anyhow.
You mentioned "procedures" that may help, Joseph, could you be more
specific? I have a limited background with Access, although I've worked on
other databases.
thanks again,
-Ned.

"Joseph Meehan" wrote in message
news:htUqg.16529$u11.3923@tornado.ohiordc.rr.com.. .
> Ned Fraser wrote:
>> I've inherited a database that is being used to store customer
>> information. We need to keep a log of customers no longer with us,
>> with no activity in several years.
>> Windows XP, Access 2003.
>> Several users are adding records at the same time, and once in a
>> while, different users get locked out of the system!
>> The key is ID, Autonumber, Indexed=yes, no duplicates. I have open
>> mode=shared, locking=edited record, and record-level locking set.
>> What else should I be looking at?
>> Thanks in advance!
>
> It is normal when more than one user is accessing and editing data in
> Access for one or more to receive an error message. Since it is possible
> that they may be editing the same record and by the time the second one is
> making a change the first one may have made a different change that the
> second one is unaware of and should know about before committing their
> change.
>
> It can be irritating at times. I might also suggest that in some
> versions of Access it is possible that they may not have even been working
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=12625
> on the same "record." If it happens a lot there are procedures that may
> help, depending on the work flow of the office.
>
> If by being locked out you mean something different, sorry I can't
> help, that never happened to any of my applications.
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=12625
>
> --
> Joseph Meehan
>
> Dia duit
>

#4 (**permalink**) 28-Jul-2006, 08:30 AM

Ned Fraser wrote:
> The users are only adding, not editing records. The records being
> added are never duplicates (the users are adding records based upon
> separate paper files), and the key is an autonumber ID, anyhow.
> You mentioned "procedures" that may help, Joseph, could you be more
> specific? I have a limited background with Access, although I've
> worked on other databases.
> thanks again,
> -Ned.
>

In my case there were several possible issues, but it is most likely
that most if not all of the issues were editing not creating new records.
I simply moved to a batch process, so those adding records. Each of my data
entry people created records on a local table with the additional
information. At the end of the day they ran up update query which edited
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=12625
the records on the back end and that was during a very slow part of the day.
That resolved almost 100% of the problems.
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=12625

I can not say if that would work for you.

BTW I am assuming that you are using a split database with each user
having their own copy of the front end on their own PC with forms, queries
and everything but the actual shared data, and one back end on the server
with the actual data.

--
Joseph Meehan

Dia duit