I'm developing an Access application which will eventually run with a back
end on a server, but for local development I have only a single PC
available.
So I've mapped a drive to a folder on my PC.
I can see the drive and the mdb file in it in my Windows Explorer, but when
I try to open the mdb, it's read-only.
If I navigate directly to the mdb on my PC (not using the mapped drive), I
can open the mdb normally (read/write).

What could be the problem?
- TIA

I assume you created a shared folder on your PC. When you did this did you
allow changes? I foret the exact term it uses but make sure the share is set
to allow users to make changes.

What is the point of mapping back to yourself anyway? If your db is already
split can't you just relink the tables when you have the server available?

Tony


"MacDermott" <(E-Mail Removed)> wrote in message
news:%23t6hBd$(E-Mail Removed)...
> I'm developing an Access application which will eventually run with a back
> end on a server, but for local development I have only a single PC
> available.
> So I've mapped a drive to a folder on my PC.
> I can see the drive and the mdb file in it in my Windows Explorer, but
> when I try to open the mdb, it's read-only.
> If I navigate directly to the mdb on my PC (not using the mapped drive), I
> can open the mdb normally (read/write).
>
> What could be the problem?
> - TIA
>

Hello MacDermott.

"MacDermott" wrote:
> I'm developing an Access application which will eventually run
> with a back end on a server, but for local development I have only
> a single PC available.
> So I've mapped a drive to a folder on my PC.
> I can see the drive and the mdb file in it in my Windows Explorer,
> but when I try to open the mdb, it's read-only.
> If I navigate directly to the mdb on my PC (not using the mapped
> drive), I can open the mdb normally (read/write).
>
> What could be the problem?

The default permissions on a shared folder allow only read access to
everyone. Check the Permissions settings on the sharing tab of the
properties window of the folder you shared.
When connecting to a folder using a share, a user has at most the
permissions that are specified there.

--
Regards,
Wolfgang

Many thanks to both of you.
It was indeed the sharing permissions which were set wrong.

Tony -
As for why I'm doing this: you're quite right that I could just link
directly. One client of mine has asked for a check that the back-end is
*not* on the local machine, or at least is on a drive with a mapped letter
which is not C. I needed this setup to test that. Another client has his
back-end on a server, and has some problems re-linking which I haven't been
able to trouble-shoot remotely. A quick work-around is for me to create a
setup on my machine with a drive structure which mirrors his. That way I
can deliver front-end changes which don't require relinking.

Thanks again!

"Wolfgang Kais" <(E-Mail Removed)> wrote in message
news:%23PTxBs$(E-Mail Removed)...
> Hello MacDermott.
>
> "MacDermott" wrote:
>> I'm developing an Access application which will eventually run
>> with a back end on a server, but for local development I have only
>> a single PC available.
>> So I've mapped a drive to a folder on my PC.
>> I can see the drive and the mdb file in it in my Windows Explorer,
>> but when I try to open the mdb, it's read-only.
>> If I navigate directly to the mdb on my PC (not using the mapped
>> drive), I can open the mdb normally (read/write).
>>
>> What could be the problem?
>
> The default permissions on a shared folder allow only read access to
> everyone. Check the Permissions settings on the sharing tab of the
> properties window of the folder you shared.
> When connecting to a folder using a share, a user has at most the
> permissions that are specified there.
>
> --
> Regards,
> Wolfgang
>
>

I use code the code here - http://www.mvps.org/access/tables/tbl0009.htm

....which is run on startup of the db and if it cannot find the linked MDB,
prompts the user to select the new MDB location and then relinks all the
table for them. It assumes that the MDB does not require a password and that
all linked tables are linked to the same MDB.

For my uses I added some lines that attempt to find the file in a default
location (which I defined) and then only prompt if it can't be found. But
that is just me.

Tony


"MacDermott" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Many thanks to both of you.
> It was indeed the sharing permissions which were set wrong.
>
> Tony -
> As for why I'm doing this: you're quite right that I could just link
> directly. One client of mine has asked for a check that the back-end is
> *not* on the local machine, or at least is on a drive with a mapped letter
> which is not C. I needed this setup to test that. Another client has his
> back-end on a server, and has some problems re-linking which I haven't
> been able to trouble-shoot remotely. A quick work-around is for me to
> create a setup on my machine with a drive structure which mirrors his.
> That way I can deliver front-end changes which don't require relinking.
>
> Thanks again!
>
> "Wolfgang Kais" <(E-Mail Removed)> wrote in message
> news:%23PTxBs$(E-Mail Removed)...
>> Hello MacDermott.
>>
>> "MacDermott" wrote:
>>> I'm developing an Access application which will eventually run
>>> with a back end on a server, but for local development I have only
>>> a single PC available.
>>> So I've mapped a drive to a folder on my PC.
>>> I can see the drive and the mdb file in it in my Windows Explorer,
>>> but when I try to open the mdb, it's read-only.
>>> If I navigate directly to the mdb on my PC (not using the mapped
>>> drive), I can open the mdb normally (read/write).
>>>
>>> What could be the problem?
>>
>> The default permissions on a shared folder allow only read access to
>> everyone. Check the Permissions settings on the sharing tab of the
>> properties window of the folder you shared.
>> When connecting to a folder using a share, a user has at most the
>> permissions that are specified there.
>>
>> --
>> Regards,
>> Wolfgang
>>
>>
>
>