All users must be admins?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a current situation some of my customers that run a particular fuel
data software that uses access databases. I noticed that all users of the
program had to be given admin rights - and this poses a severe security risk
I know. I've tried granting permissions on the files and folders that are
affiliated with the program, along with that of the MS Office folder, but
there are forever errors coming up, sometimes a Jet(?) error or a runtime
error. After talking to the software programmer and designer I was informed
that it was due to a temporary folder that's created by Access. According to
him the temp folder only carries Admin permissions. I know this can't be
right. Unfortunately I don't have anything further to add as far as error
codes go except for error 3051. I'm afraid I'm going to get a call telling
me that someone's network is down because someone with admin rights decided
to reak havoc on the server.

Is there anyone out there who might be able to shed some light on this for
me? I know I'm not bringing much to the table to work with, but I'll get
more info as soon as I can.

Thanks in advance,
Dave
 
They need all permissions to the folder the mdb is in, so the app can create
or delete the LDB locking file (which is automatic). That folder can be placed
on it's own somewhere.

Access itself does not create any other "temporary files or folders" and
certainly not folders, though the app may be written to for all I know.

Apart from needing read/write/delete permission to the folder the mdb is
stored in, it is not usual to grant admin permissions to users.

I'm a bit rusty on LDB's (someone will correct me if I'm wrong) but LDB's
appear in a quick data-update test to be associated with the Front-End not the
Back-End?

Chris
 
As far as my experiance is concerned, an LDB is created eveytime an MDB is
accessed (i don't use MDE so I don't know). I get an LDB for both my front
end and back end.
 
I get an LDB for both my front end and back end.Quite right. Dunno what I did. Anyway the effect for "dtremain" is that all
mdb folders need read/write/delete.

If the table links are made via UNC naming, I suppose it would be safer than a
"shared drive".
Chris
 
IIRC you do not get one for the db, if you open the db exclusive
read-only (/excl, /ro).

HTH,
TC
 
Access uses the user temp folder. You would hope that your
users have access to their own temp folder, but who
knows? Look for a file called Jet<something>.tmp,
normally 0 bytes long while you have Access open and
aren't doing anything.

On my pc as I write, c:\temp\jet52d5.tmp

(david)
 
3501 error could be due to changed access rights to folder

Hi,

Having got a hint from the above posts, I discovered my problem was that the Network admin changed the password for all users accessing the network.

Since they couldn't access the backend of the Database, then they get this 3501 error. I had the backend mapped to a drive letter such as S: for Sales. IF this wasn't Mapped (referenced?), or the password had changed then error 3501 or can't find the database occured.

Summary:
3501 was due to no read/write access(Permission) to Folder which has the backend Database(The linked tables) denying users access to the Database App.
Solution:
Check if the user can access the folder in question, and get right into the folder in question, then try again, if successful. If not, then enter password or new Password for the Folder access.

At least this was the problem for me, and was the solution to fixing it, and here I was thinking it was because I was messing around with the .ldb file (in Tracking users who are logged in).
 
Back
Top