Different Computer, Can't Open db with Same Username & Password

[tbl]

After getting a split, secured MS Access db working well,
with the Front End, Back End, and MDW files in a directory
right off the C: drive, I take the files home, put them in a
matching C: drive directory, and find that I can only open
the db if I have logged on to the Win2k computer with an
admin-level account. If I log on to the computer with a
limited-user level account, even using the same username and
password for the the db, no go.

So now I need to understand the interplay between the
computer accounts and the db's accounts, for Win2k.

Anyone?

 

[Scott McDaniel]

After getting a split, secured MS Access db working well,
with the Front End, Back End, and MDW files in a directory
right off the C: drive, I take the files home, put them in a
matching C: drive directory, and find that I can only open
the db if I have logged on to the Win2k computer with an
admin-level account. If I log on to the computer with a
limited-user level account, even using the same username and
password for the the db, no go.

Do non-admin users have the necessary permissions for that directory (the one off the C: drive on the home machine)?
Users require Read/Write/Create/Destroy permissions on that folder. Admins users would have those rights, but not
necessraily "normal" users. Check the folder's Security tab in Windows Explorer and make sure that the user (or a Group
of which that user is a member) has those permissions for the folder.

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com

 

[Keith Wilby]

After getting a split, secured MS Access db working well,
with the Front End, Back End, and MDW files in a directory
right off the C: drive, I take the files home, put them in a
matching C: drive directory, and find that I can only open
the db if I have logged on to the Win2k computer with an
admin-level account. If I log on to the computer with a
limited-user level account, even using the same username and
password for the the db, no go.

So now I need to understand the interplay between the
computer accounts and the db's accounts, for Win2k.

The user needs Change permissions to the host folders. Might that be it?
Any errors to report?

Keith.
www.keithwilby.com

 

[tbl]

Thanks for the reply, Scott.

Replies in-line...

Do non-admin users have the necessary permissions for that directory
(the one off the C: drive on the home machine)?

Yup.


Users require Read/Write/Create/Destroy permissions on that folder.
Admins users would have those rights, but not
necessraily "normal" users. Check the folder's Security tab in Windows
Explorer and make sure that the user (or a Group
of which that user is a member) has those permissions for the folder.

That folder has "Anyone" permissions.

 

[tbl]

Thanks for replying, Keith.

My replies in-line...

The user needs Change permissions to the host folders. Might that be it?

That directory is set to "Anyone" for all permissions in
Win2k.

Any errors to report?

Yes, come to think of it!

When I use the link that has all 3 parts in it, I get:

"Microsoft Access can't find the database file
'C:\CRPD\CRPD.mdb.'"

If I dblclick on the mdb file itself, I get:

"The Microsoft Jet database engine cannot open the
file 'C:\CRPD\CRPD.mdb'. It is already opened
exclusively by another user, or you need permission
to view its data."

Stumped!

 

[tbl]

Thanks for replying, Keith.

My replies in-line...





That directory is set to "Anyone" for all permissions in
Win2k.




Yes, come to think of it!

When I use the link that has all 3 parts in it, I get:

"Microsoft Access can't find the database file
'C:\CRPD\CRPD.mdb.'"

If I dblclick on the mdb file itself, I get:

"The Microsoft Jet database engine cannot open the
file 'C:\CRPD\CRPD.mdb'. It is already opened
exclusively by another user, or you need permission
to view its data."

Stumped!

Woops! Make that "Everyone", not "Anyone".

 

[tbl]

After getting a split, secured MS Access db working well,
with the Front End, Back End, and MDW files in a directory
right off the C: drive, I take the files home, put them in a
matching C: drive directory, and find that I can only open
the db if I have logged on to the Win2k computer with an
admin-level account. If I log on to the computer with a
limited-user level account, even using the same username and
password for the the db, no go.

So now I need to understand the interplay between the
computer accounts and the db's accounts, for Win2k.

Well, here's a looming possibility: I had forgotten that
the work and the home versions of Access are different. Home
is 2000, and work is 2002. At work, the setting to save in
2000 format is checked, but I don't know if that is designed
to apply to the security features. If it is, then something
ain't according to Hoyle.

At home, I had to be a Windows admin to open the db in
Access, and even then I couldn't make any design changes.

When I got back to work this morning, I put the "home" files
(MDBs) on the C: drive, and Access went wonky when I tried
to open the files. I can't remember just now what
constituted wonky, but I had to roll back to the previous
backup and *import* the data from the "home" version. To
irritate myself further, I flubbed the import, and had to do
it a second time to get it right.

If anyone knows of any issues moving between these two
versions of Access, I'd sure like to hear about 'em.