Douglas J. Steele said:
The users require Change access (at least Read, Write, eXecute and Delete)
on the folder where the MDB file exists.
There's no system process that I'm aware of that needs to be running.
There likely are ways to stop certain DLLs from running, but I don't think
that's very common.
What symptoms are you observing that make you think that might be the
case?
I have created a program (not MS Access) that uses an Access Database to
provide content and track what the user is doing. On start, the application
launches an Inno setup to install the database to the user's profile. The
application is not able to read any information out of the database. The
program uses a u32 (which is essentially a dll wrapped for consumption by
this type of an application) to make a DSN'less connection. The component
is known to fail in instances where the path to the database is excessively
long, but I am pretty sure the profile folder name is not long enough to
cause that problem in this instance. I have never heard of any other cause
of failure in the u32.
I knocked together a little diagnostic application last night in the 45
minute window I had before the user went to bed and was able to determine
that a query that should return information every time was not returning
data. I did not think to get the diagnostic to raise error messages (the
rush was to just get it built to get some pointers to what the problem could
be). I doubt I'll get another shot at this particular user's machine, so
I'm sort of scrambling to try to find a way to duplicate the problem so that
we can solve it for the next user.
Thanks!
-Amy
