Struggling to enable more than one user

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jay - 21 May 2006 19:25 GMT

Hi,

I've been struggling to get a db usable by more then one person. My last
post on another Access ng is as follows: Does the database really have to be
split? I only want two users to have simultaneous use. This is what I have
done so far:

- Checked security settings on the folder (2nd tab in
the properties window), and confimed that the users have modify,
read, write, execute permisions.

- Ensured that 'shared' access is checked in Tools-Options

Both users can have the mdb open at the same time, but if either tries to
use a form that the other is using (which will probably be showing some
query output) they get the following error:

'Run-time error '3009'
'You tried to lock tabkle 'tblContactList' while opening it, but the table
cannot be locked because it is currently in use. Wait a moment, and then
try the operation again.'

I have tried all the different record-locking options, but the error
persists.

If anyone can advise how I can enable 2-user simultaneous use without the
above error I would be *so* grateful:-)

Hopefully yours,

-Jay-

Reply to this Message

Douglas J. Steele - 21 May 2006 21:06 GMT

Any reason you don't want to split? It's the best way to go, even with only
two users. (Heck, I have a bunch of applications written strictly for my own
personal use, and they're all split...)

Is it only the one form that's causing problems? What's the relationship
between that form and tblContactList?

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)

> Hi,
>
[quoted text clipped - 28 lines]
>
> -Jay-

Reply to this Message

Jay - 21 May 2006 21:53 GMT

On 21/5/06 21:06, in article uttwIHRfGHA.3488@TK2MSFTNGP02.phx.gbl, "Douglas
J. Steele" <NOSPAM_djsteele@NOSPAM_canada.com> wrote:

> Any reason you don't want to split? It's the best way to go, even with only
> two users. (Heck, I have a bunch of applications written strictly for my own
> personal use, and they're all split...)

I just wondered if it was even required, for just 2 users. And if not, if I
can't get it to work without being split, what chance getting it to work
after being split?

> Is it only the one form that's causing problems?

Well, the way the db's been set up, you can't progress without going through
the form. (weird single field, single record tables (from make table
queries) that I'm trying to get my newbie head round)

> What's the relationship between that form and tblContactList?

The form basically displays the fields from tblContactList, one of which is
chosen to be the criteria for a subsequent criteria. (pick a contact & see
their details kind of thing).

I did what was detailed in my o.p, then got 2 laptops side by side & tried
simultaneous use myself & got the error I mentioned.

And I just don't know what to do?

Any help *greatly* appreciated.

Regards

Jay

Reply to this Message

Douglas J. Steele - 22 May 2006 00:40 GMT

> On 21/5/06 21:06, in article uttwIHRfGHA.3488@TK2MSFTNGP02.phx.gbl,
> "Douglas
[quoted text clipped - 10 lines]
> can't get it to work without being split, what chance getting it to work
> after being split?

If you're doing any "design"-type stuff in your application (redefining
forms and the like), splitting is ofter mandatory, since you must have
exclusive access in order to be able to make design changes.

>> What's the relationship between that form and tblContactList?
>
> The form basically displays the fields from tblContactList, one of which
> is
> chosen to be the criteria for a subsequent criteria. (pick a contact & see
> their details kind of thing).

What exactly does the form do? Any code behind it that is trying to lock?

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)

Reply to this Message

Jay - 22 May 2006 22:02 GMT

On 22/5/06 00:40, in article epQ$7$SfGHA.356@TK2MSFTNGP02.phx.gbl, "Douglas
J. Steele" <NOSPAM_djsteele@NOSPAM_canada.com> wrote:

>> On 21/5/06 21:06, in article uttwIHRfGHA.3488@TK2MSFTNGP02.phx.gbl,
>> "Douglas
[quoted text clipped - 23 lines]
>
> What exactly does the form do? Any code behind it that is trying to lock?

I think I may have seen what the problem may be. The form is based on a
table made by a make table query. The user selects his staff initials in
the previous form , initials which are then used as the criteria in the make
table query. The made table (tblContactList) is merely a list of that staff
members contacts . So another user can't use the table at the same time as
it is (temporarily) based on another users initials. The made table is then
autmotically deleted with a macro controlled delete query when the user
exits the form (?)...thus ebanbling the nect user to select his initials &
the table is made from his initials.

I know I'm a newbie to Access but am I right in thinking this is plain
wrong? God knows why there's a make table query that simply copies filtered
records from the main contacts table. Why make a table when this can be done
by query? Why not have the staff table & contacts table linked one to many
& the form (staff contacts) based on a query on the linked tables? Therefore
there wouldn't be this weird temporary 'made' table.

I would welcome your comments Doug.

Regards

Jay
___

Reply to this Message

Douglas J. Steele - 23 May 2006 22:48 GMT

> On 22/5/06 00:40, in article epQ$7$SfGHA.356@TK2MSFTNGP02.phx.gbl,
> "Douglas
[quoted text clipped - 43 lines]
> exits the form (?)...thus ebanbling the nect user to select his initials &
> the table is made from his initials.

Any particular reason for the make table query? In a non-split application,
that's almost guaranteed to cause problems. In a split application, you have
the option of storing the data in the front-end, or you can even use a
temporary database (as Tony Toews illustrates at
http://www.granite.ab.ca/access/temptables.htm)

> I know I'm a newbie to Access but am I right in thinking this is plain
> wrong? God knows why there's a make table query that simply copies
[quoted text clipped - 6 lines]
> Therefore
> there wouldn't be this weird temporary 'made' table.

Simply filtering would likely be the best approach. Temporary tables are
seldom the correct approach (unless required for performance reasons)

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)

Reply to this Message