linked tables between 2 secured mdbs

[ragtopcaddy via AccessMonster.com]

HAPPY NEW YEAR!!!

I have 2 secured mdbs, both sharing the same workgroup. I have linked tables
between both mdbs. How do I ensure that when vba procs run in one of the
secured mdbs, it will be able to write data to linked tables from the other
secured mdb? I would have thought that, once logged into one of the mdbs via
a shortcut to the appropriate workgroup, a permitted user would have
permissions to write to the linked table, so long as both mdbs are secured
via the same workgroup.

Thanks,

Bill

--
Bill Reed

"If you can't laugh at yourself, laugh at somebody else"

Message posted via AccessMonster.com

 

[Rick Brandt]

HAPPY NEW YEAR!!!

I have 2 secured mdbs, both sharing the same workgroup. I have linked tables
between both mdbs. How do I ensure that when vba procs run in one of the
secured mdbs, it will be able to write data to linked tables from the other
secured mdb? I would have thought that, once logged into one of the mdbs via
a shortcut to the appropriate workgroup, a permitted user would have
permissions to write to the linked table, so long as both mdbs are secured
via the same workgroup.

That is exactly how it should work. Have you tried it? Did you have problems?

 

[ragtopcaddy via AccessMonster.com]

Rick,

Thanks for the quick response.

I just got back to my desk from Christmas vacation. I haven't examined the
user's error msgs yet, but a procedure that writes to a linked table in one
of the dbs failed to write the data and produced an error msg. I just wanted
to be sure that there are no additional issues with this scenario before I go
on a wild goose chase. As long as it should work without additional
accommodations to security, then I won't waste time looking for the solution
there.

Thanks for your advice,

Bill

HAPPY NEW YEAR!!!

[quoted text clipped - 5 lines]

permissions to write to the linked table, so long as both mdbs are secured
via the same workgroup.

That is exactly how it should work. Have you tried it? Did you have problems?

--
Bill Reed

"If you can't laugh at yourself, laugh at somebody else"

Message posted via AccessMonster.com

 

[ragtopcaddy via AccessMonster.com]

He got error 3051 "another user has the db open" but there's no ldb there so..
"or you need permission to view its data".

HAPPY NEW YEAR!!!

[quoted text clipped - 5 lines]

permissions to write to the linked table, so long as both mdbs are secured
via the same workgroup.

That is exactly how it should work. Have you tried it? Did you have problems?

--
Bill Reed

"If you can't laugh at yourself, laugh at somebody else"

Message posted via AccessMonster.com

 

[Rick Brandt]

He got error 3051 "another user has the db open" but there's no ldb there so..
"or you need permission to view its data".

Sounds like he (or someone else) has insufficient permissions to the folder
where the other MDB resides. If someone opens that file that does not have
create file permissions on the folder then they will be opening the file as read
only, no LDB file is created, and all others are locked out.