[AccessD] FE on Server for Each User

Good Point!

They may be getting specific instructions from their parent company, but
I'll certainly see if they are allowed to do this.

:-)
Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Friday, May 11, 2007 6:24 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] FE on Server for Each User

This is a windows security issue, but that doesn't mean that a plain old
user cannot have rights to a specific directory, even under the C: drive.
An administrator has to set the rights for the same dir you used to use, so
that that specific user, or even a flunky user group, can have full rights
to exactly and only that directory.  Having rights to a directory is not the
same as having admin rights to the machine.

John W. Colby
Colby Consulting
www.ColbyConsulting.com
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Friday, May 11, 2007 5:51 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] FE on Server for Each User

Hi John,

Having a single folder on the C drive is what I had before:  The path was
C:\PSISystemClient, and all the other folders and files were in this one.
But when they started to remove local admin rights, the users could no
longer add anything directly below the C: drive, which is when they started
getting 'Can't Connect' error messages.  They started this last week, and we
had a brainstorming solution meeting yesterday.

Without local admin authority, there is a folder at C:\Documents and
Settings\[UserName]\ that users can add anything into.  If the UserName
folder is actually the same as the User Name, I can use that.  But, the
migration tool they used set up the user folders with the previous user
names, which didn't follow any convention at all.  To track that, I'd have
to create and maintain a table of actual user names and corresponding folder
names, which is even more problematic.

I guess this is a Windows security problem, not an Access problem.

Dan

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com