F
Fredrick A. Zilz
I don't know what I am doing wrong. I had an Access 2000 database FE BE
configuration. I converted them to Access 2002-2003 by importing them to a
new database created with a user joined to a new MDW. The FE databases now
works fine, but the permissions on the back end are notcorking consistently.
I can not seem to keep from having the database locked. I now have the BE
database set so that all groups have all rights to all tables. I still have
users that can't update or add records. I sign in to thier account on my
computer and I have no problem. I sign in on their computer and they can not
seem to change anything.
Also, I had everyone close thier access client, yet I still could not
rename, copy or delete the backend database. I finally removed the share on
the network folder, then renamed, then restored the share. I can not figure
out what is going on. I am starting to think that access is continuing to
maintain a connection to the backend database from users using Office 2003
on Windows 2000 sp4 (with jet 8.0 service pack).
Help.
configuration. I converted them to Access 2002-2003 by importing them to a
new database created with a user joined to a new MDW. The FE databases now
works fine, but the permissions on the back end are notcorking consistently.
I can not seem to keep from having the database locked. I now have the BE
database set so that all groups have all rights to all tables. I still have
users that can't update or add records. I sign in to thier account on my
computer and I have no problem. I sign in on their computer and they can not
seem to change anything.
Also, I had everyone close thier access client, yet I still could not
rename, copy or delete the backend database. I finally removed the share on
the network folder, then renamed, then restored the share. I can not figure
out what is going on. I am starting to think that access is continuing to
maintain a connection to the backend database from users using Office 2003
on Windows 2000 sp4 (with jet 8.0 service pack).
Help.