Trying to update the Access Database

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

Guest

I have created an Access database with a Back-end. The back-end has files
imported into it once a week. The problem I am having is when we try to
update the back-end with the new data, people are still logged into it. I
get a message saying the datbase is open in READ ONLY MODE and changes can
not be made.
At the present time we have to call IS and ask them to find out which users
are logged onto the database.

There are no logins or passwords to the database. The database is only for
reference use (no data input required) but quite frequently used. My
question is if there is a way without killing the user through Windows that I
can close the database and close the user connections if still connected? I
am trying to automate the task of importing the data and need a quick way of
getting a user off (which problably left his/her machine on for the weekend)
so I can execute my task.

Thanks for any help!
 
TC,

Thanks for the response. Is there another way, I know that idea will not
fly the company only wants 2 people having full permissions to the shared
directory. Everyone else is read. I have already suggested that idea. Is
there any tables where it show users linked. Any way of just locking the
database whether there is a user in it? Anyway of closing a user connection
to the database?
 
By design of Microsoft Access, every "update" user of the database
needs full permissions (read/write/create/delete) to the folder in
which the database lives. This is so that Access can create and manage
the locking (.LDB) file that is required for read/write operation. If
a user does not have full access to the folder, Access can not create
the locking file, so it will open the database in read only mode.

As for your last three questions, I'm not sure that I understand them:
- Is there any tables where it show users linked.
- Any way of just locking the database whether there is a user in it?
- Anyway of closing a user connection to the database?

What are you actually trying to achieve from an "end user" viewpoint?

HTH,
TC (MVP Access)
http://tc2.atspace.com
 
TC,

Again thanks for the reply. A will try to make my question direct. If a
user leaves on a machine over the weekend and is still accessing the back-end
I can not update the back-end! It comes up READ ONLY. I would like to know
if there is a way I can disconnect the user from the back-end without
changing permissions on the directory.
 
Ok, I understand.

There's no way to forcibly disconnect that user, except by rebooting
the back-end PC - which might corrupt the database! (So don't do that.)

You can, however, write code within the front-end database, which looks
for a "go away" signal of some kind. (That signal might be, for
example, a record in a special table. You add that record to that
table, when you want he users to all go away.) Then the front-ends see
that signal, and quit themselves automatically. But you have to write
this feature into your front-end database code.

Try this for more information:
http://groups.google.com/groups/search?q=disconnect+a+user+group:*access*

HTH,
TC (MVP Access)
http://tc2.atspace.com
 
TC,

Thanks that was what I was looking for, I will give it a shot. Thanks for
all the replies.
 
Back
Top