Problem with Linked Tables

[mela]

I have created a separate database for external dept. use that links to
tables in another database for internal dept. use. I have placed the second
public database on a shared drive, whereas the non-public database is on a
locked down drive. A co-worker notified me this morning that she is getting
an error message and that the path is invalid. Do users need to have
permissions to the drive where the non-public database resides? If yes, then
the linked table option for distributing to others won't work. Thanks.

 

[Tom van Stiphout]

On Wed, 30 Dec 2009 07:28:01 -0800, mela

I am assuming each user has the front-end on their local machine.
For the back-ends, users need to have read, write, and create
privileges. Why create? Because they may be the first in, and have to
create the .ldb file.

-Tom.
Microsoft Access MVP

 

[mela]

No, I have not split the database. Instead, at the suggestion of Joan Wild
in another posting, I created another database and removed all tables, etc
and left in only the read only user form for public access. I am trying to
do this very low maintenance without distributing anything to the users. I
am working with a field sales force - they need simplicity.

I am working on trying to figure out access via a DAP on our intranet as a
second option. Thanks.

 

[Joan Wild]

The 'public' database still needs linked tables (linked to the backend)
- and users need the create permission on the backend folder.

Joan Wild