In our small office, we have installed a
network-attached-storage (NAS) device, and have tried
putting our main db back-end on it so that others in the
office can use it. Our PCs all run WindowsXP with all the
patches and service-packs, and OfficeXP (2002), all patched.

The back-end has been residing on the D: drive of my
machine, with a co-worker accessing it there with no
problems. We've had the NAS for over a year now, and after
several attempts, have never gotten it to work with our db.

Whenever we try it on the NAS, only the first-on user can do
anything--the next person gets the old "already in use"
message.

I don't know much about networks, and I suppose this is more
of a network problem than an Access problem, but if anyone
cares to throw us a bone...

--
Thanks,
croy

The users need read/write/create permissions on the folder where the
backend is located. This is so the associated ldb file can be created.
Without the ability to create this file, the mdb will be opened
exclusively by the first user in.

Joan Wild


croy wrote:
> In our small office, we have installed a
> network-attached-storage (NAS) device, and have tried
> putting our main db back-end on it so that others in the
> office can use it. Our PCs all run WindowsXP with all the
> patches and service-packs, and OfficeXP (2002), all patched.
>
> The back-end has been residing on the D: drive of my
> machine, with a co-worker accessing it there with no
> problems. We've had the NAS for over a year now, and after
> several attempts, have never gotten it to work with our db.
>
> Whenever we try it on the NAS, only the first-on user can do
> anything--the next person gets the old "already in use"
> message.
>
> I don't know much about networks, and I suppose this is more
> of a network problem than an Access problem, but if anyone
> cares to throw us a bone...
>

On Tue, 10 Nov 2009 15:05:48 -0500, Joan Wild
<(E-Mail Removed)> wrote:

> The users need read/write/create permissions on the folder where the
> backend is located. This is so the associated ldb file can be created.
> Without the ability to create this file, the mdb will be opened
> exclusively by the first user in.

Thanks Joan.

As near as we can tell, all of us have read/write/create
permissions on that directory. It gets a little confusing
for me, as the NAS has its security stuff, Windows has its,
and were also running a Novell network, and I assume *it*
has security stuff as well.

But when either of us logs in (alone), there *is* an ldb
file created in the NAS directory where the back-end
resides.

I'm going to look thru all the permissions stuff (that stuff
that I understand) again, and see if anything pops out.

Thanks for the help.

--
croy

croy <(E-Mail Removed)> wrote:

>As near as we can tell, all of us have read/write/create
>permissions on that directory. It gets a little confusing
>for me, as the NAS has its security stuff, Windows has its,
>and were also running a Novell network, and I assume *it*
>has security stuff as well.
>
>But when either of us logs in (alone), there *is* an ldb
>file created in the NAS directory where the back-end
>resides.
>
>I'm going to look thru all the permissions stuff (that stuff
>that I understand) again, and see if anything pops out.

One way of testing this is to see if a few of the users can create,
updated and delete .txt files using Notepad. If not then there is a
permissions problem.

However It may be that Access use of phantom locks on the LDB file
isn't supported by the NAS. This has been a problem in years past
with older versions of Linux servers and other non Microsoft servers.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a free, convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/

"Tony Toews [MVP]" <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> However It may be that Access use of phantom locks on the LDB file
> isn't supported by the NAS. This has been a problem in years past
> with older versions of Linux servers and other non Microsoft
> servers.

I would simply never store a Jet/ACE file on anything but a native
Windows file system accessed via native Microsoft SMB networking.
Thus, no Linux/SAMBA, and no Novell. This policy has served my
clients very well over the years.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

On Tue, 10 Nov 2009 15:05:48 -0500, Joan Wild
<(E-Mail Removed)> wrote:

>The users need read/write/create permissions on the folder where the
>backend is located. This is so the associated ldb file can be created.
> Without the ability to create this file, the mdb will be opened
>exclusively by the first user in.

Investigation has shown that the ldb file is getting created
by the first user on.

--
croy

On Sun, 22 Nov 2009 14:57:54 -0700, "Tony Toews [MVP]"
<(E-Mail Removed)> wrote:

>croy <(E-Mail Removed)> wrote:
>
>>As near as we can tell, all of us have read/write/create
>>permissions on that directory. It gets a little confusing
>>for me, as the NAS has its security stuff, Windows has its,
>>and were also running a Novell network, and I assume *it*
>>has security stuff as well.
>>
>>But when either of us logs in (alone), there *is* an ldb
>>file created in the NAS directory where the back-end
>>resides.
>>
>>I'm going to look thru all the permissions stuff (that stuff
>>that I understand) again, and see if anything pops out.
>
>One way of testing this is to see if a few of the users can create,
>updated and delete .txt files using Notepad. If not then there is a
>permissions problem.
>
>However It may be that Access use of phantom locks on the LDB file
>isn't supported by the NAS. This has been a problem in years past
>with older versions of Linux servers and other non Microsoft servers.


Thanks, Tony!

It's working!

From my machine, in Windows Explorer, I went to properties
for the NAS directory where the back-end is stored, and
selected "Advanced", and set "Everyone" for "Full control",
and now it works. That's probably a little over-the-top,
but as time allows, I'll try trimming that back.

--
croy