multiple users & data entry

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm having an issue with record locking and/or shared mode. My d-base has a
form that users do data entry on. Ideally, I'd like it so all users can
enter data at the same time. But there seems to be problems since they use
the same form. The alternative is to lock records and make the database open
in exclusive mode only. My problem is that when I select Exclusive Mode on
Tools, Options, Advance, the other users still open the database. I was
hoping to restrict it. When I set the default record locking to edited
record, nothing appears to happen. Is there something I can use in VB that
will force the database to be restricted to 1 user at a time. D-base is on a
network.
 
I'm having an issue with record locking and/or shared mode. My d-base has a
form that users do data entry on. Ideally, I'd like it so all users can
enter data at the same time. But there seems to be problems since they use
the same form. The alternative is to lock records and make the database open
in exclusive mode only. My problem is that when I select Exclusive Mode on
Tools, Options, Advance, the other users still open the database. I was
hoping to restrict it. When I set the default record locking to edited
record, nothing appears to happen. Is there something I can use in VB that
will force the database to be restricted to 1 user at a time. D-base is on a
network.
Click to expand...

First off, you should CERTAINLY use the Database Splitter Wizard to
split the database into a shared "backend", containing the tables, and
a Frontend; each user should have their own copy of the frontend.

Access is multiuser by default. Unless multiple users are attempting
to update the same *RECORD* at the same time - not the same database,
not the same table, but the exact same record - there is usually no
conflict; even if they are updating the same record, the worst that
will happen is that the second user to try to save a record will get a
warning message popping up that another user has modified the data
since they first brought it up. That's what "edited record locking"
means - that multiple users can freely edit the database, just so
they're not stepping *directly* on each others' toes.

Could you explain why you want to use the much more restrictive
exclusive option?

John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps
 
I was grasping for a solution. When you mention "each user should have their
own copy of the frontend", how would that be deployed? Would I put a copy
for each clinic on the same network drive? These clinics are located in
different towns.

Thanks so much for resonding and providing information.
 
tag said:
I was grasping for a solution. When you mention "each user should have their
own copy of the frontend", how would that be deployed? Would I put a copy
for each clinic on the same network drive? These clinics are located in
different towns.
Click to expand...

Does that mean you are running this over a WAN? That will never work with an
Access/Jet file unless you use remote software like Terminal Server or Citrix
over Terminal Server. A WAN just isn't reliable or fast enough for an Access
file share application.
 
Back
Top