By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,849 Members | 2,169 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,849 IT Pros & Developers. It's quick & easy.

locked table

P: n/a
i have a macro that imports ables omn opening of the Database
the problem is when a user has the database open
the second user gets an error message cant lock another user has the
table open

is it possible to get round this


Jan 16 '06 #1
Share this Question
Share on Google+
3 Replies

P: n/a
you have two choices:

1. Use a seperate front end for each user, each with local copies of
imported tables
2. Change the code to import the data, not the table

but a better approach is to question this practice, why do you need to
do this? i'm willing to bet that there is a better approach to take to
solve what you are trying to achieve. For example, why not just have a
linked table to the data source you are importing at every login...

Jan 16 '06 #2

P: n/a
Thanks very much for your suggestions
i have now linked the tables not imported them
this resolves the problem of the table not locking
Slowed the opening of the book but cant have it all
again thank you


Jan 17 '06 #3

P: n/a
Happy to help!

Linking tables does slow down an access app, because instead of having
all the data on a local machine it needs to be constantly pulled across
the network from the backend. However linking is pretty essential for a
multi user environment where there can be concurrent updates by
different users. But there are ways of speeding up things... by prudent
use of recordsets, unbound forms, stored procedures etc.

Jan 17 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.