Re: Issue with path / permissions for linked table
- From: "Allen Browne" <AllenBrowne@xxxxxxxxxxxxxx>
- Date: Thu, 13 Dec 2007 23:17:25 +0900
It doesn't have to be this issue, but last time experienced it, the network had been setup wrongly. There were mutiple shares to the same folder, one of which was read-only. The drive letter was assigned wrongly on the machine that got the error.
If you are certain it's not that issue, perhaps someone else can suggest something.
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"ormazd" <ormazd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F8A43BA2-ECF6-4E28-B564-90649E60A618@xxxxxxxxxxxxxxxx
Right. But, the users don't have permission issues when using the S: driveto group, rather than allenbrowne at mvps dot org.
path to the same table. Only when using the UNC...?
"Allen Browne" wrote:
The UNC path is generally the best solution.
You can get that error message if the user does not have adequate
permissions on the share. If they don't have permission to create a file,
Access can't create the LDB, and you get that message.
"ormazd" <ormazd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:723B2750-18BC-4D11-81EE-9ED47E002E69@xxxxxxxxxxxxxxxx
> This is a new one for me. I have a shared database with linked tables.
> Both
> databases reside on our share drive. The path for the linked file is > set
> to
> S: drive, which is the default for most employees. Our HR department,
> however, has the S: drive mapped to their own share. When the HR folks
> try
> to use this shared database, they cannot access the linked tables.
>
> In the past, I have worked around this by using UNC conventions for the
> linked tables (\\server\path\filename). This time, however, when I > made
> that
> change, the users started getting an error message "The Microsoft Jet
> engine
> cannot open the file. It is already opened exclusively by another > user,
> or
> you need permission to view its data."
>
> I would appreciate any help if someone has encountered a similar
> situation.
.
- Follow-Ups:
- Re: Issue with path / permissions for linked table
- From: ormazd
- Re: Issue with path / permissions for linked table
- References:
- Re: Issue with path / permissions for linked table
- From: Allen Browne
- Re: Issue with path / permissions for linked table
- From: ormazd
- Re: Issue with path / permissions for linked table
- Prev by Date: Re: Issue with path / permissions for linked table
- Next by Date: Re: Issue with path / permissions for linked table
- Previous by thread: Re: Issue with path / permissions for linked table
- Next by thread: Re: Issue with path / permissions for linked table
- Index(es):
Relevant Pages
|