Using Reports in a Shared Database

[Alex SF]

I used the security wizard to set up a shared database which is
accessed by several users. Record-level locking is working fine to
allow multiple users to enter data at the same time. However, it is
not possible to run reports if anyone else is entering data: Access
gives an error message that it can't lock the table underlying the
report as another user is editing it. Is there an easy fix for this?

Thanks!

[Rick Brandt]

Alex SF wrote:

I used the security wizard to set up a shared database which is
accessed by several users. Record-level locking is working fine to
allow multiple users to enter data at the same time. However, it is
not possible to run reports if anyone else is entering data: Access
gives an error message that it can't lock the table underlying the
report as another user is editing it. Is there an easy fix for this?

Thanks!

What is going on within the report? It is not necessary to "lock a table" just
to run a report. That error would normally indicate that some sort of design
change was being attempted.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[engles]

On Apr 17, 5:24 pm, "Rick Brandt" <[e-mail]:

Alex SF wrote:

I used the security wizard to set up a shared database which is
accessed by several users. Record-level locking is working fine to
allow multiple users to enter data at the same time. However, it is
not possible to run reports if anyone else is entering data: Access
gives an error message that it can't lock the table underlying the
report as another user is editing it. Is there an easy fix for this?

Thanks!

What is going on within the report? It is not necessary to "lock a table" just
to run a report. That error would normally indicate that some sort of design
change was being attempted.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

It's not clear from your post if all users open the same file. If
they are, you need to split the database and provide each user with
their own copy of the front-end.

-- Larry Engles