Hi Jeff,
Yes ... I've read quite a bit about network issues with Access. The
applications I'm building right now aren't intended to be multi-user; I just
want to be able to install them on a target machine and not have a problem
if the user of that machine wants to have a limited account use the program,
too. I discovered this when setting up the application for use on *my*
system - kind-of by accident, if you will.
After the advice given previously I moved the data directory to a common
location that all users can get at. Here's what I found that was
interesting though.
I figured that if I created the following path and the limited user could
create files there that this would solve the problem.
BasePath = "C:\Documents and Settings\All Users\Application Data\SSD\WinFF"
I used a DOS session AND a Windows Explorer (from the limited account) to
verify that files could be created in WinFF. No problem, right? Wrong.
When I ran the OpenDatabase() call using this path (and, of course the MDB
name appended) Jet gave up with a {*filter*} lock error. Kind of had me stumped
until I noticed that "Application Data" level directory is invisible to the
limited account. What was interesting was that I could actually get below
that path in both the DOS session and Explorer if I explicitly typed the
full path. However if I climbed down one level at-a-time in both the DOS
session and Explorer "Application Data" was not visible so I could climb no
lower.
Instead, I set the base path here:
BasePath = "C:\Documents and Settings\All Users\Documents\SSD\WinFF"
In this case I could ladder-step all the way down to that directory and
create files there in the limited account - and Jet allowed opening the MDB
file in that directory.
The best I could figure is that Jet would not allow opening of the MDB file
if any intermediate directory was marked hidden. Not sure what mechanism
was being violated there - but it doesn't really matter, the 2nd path is
fine as far as my application is concerned. Maybe I'll research it one of
these daze when I have nothing better to do.
-bruce ;-)
Quote:
>> Sure enough ... that's it all right. Thanks. Now I need to figure out
>> how
>> to grant that security without having to create a directory share. XP
>> Pro
>> doesn't seem to want to allow me to set directory permission (there's no
>> Security tab on the Properties Page - the machine is running in a
>> workgroup,
>> not a domain).
> Using an Access database over a network (for a multi-user situation) is
> pretty much asking for pain. I maintain an app that has maybe 3 concurrent
> users at most, and it's okay, but I've dealt with apps that have more
> users and it can be...unpleasant.