Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Security / January 2007

Tip: Looking for answers? Try searching our database.

linked tables between 2 secured mdbs

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
ragtopcaddy - 02 Jan 2007 15:27 GMT
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

Signature

Bill Reed

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

Rick Brandt - 02 Jan 2007 15:48 GMT
> 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?

Signature

Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt   at   Hunter   dot   com

ragtopcaddy - 02 Jan 2007 15:56 GMT
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 - 3 lines]
>
>That is exactly how it should work.  Have you tried it?  Did you have problems?

Signature

Bill Reed

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

ragtopcaddy - 02 Jan 2007 17:58 GMT
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 - 3 lines]
>
>That is exactly how it should work.  Have you tried it?  Did you have problems?

Signature

Bill Reed

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

Rick Brandt - 02 Jan 2007 18:10 GMT
> 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.

Signature

Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt   at   Hunter   dot   com

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.