[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

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

I think a simpler solution would be a directory on the PC that their user
has read/write rights on, with rights to create subdirs, copy files etc.
The same name folder on each workstation.  Thus the user does not have admin
rights, just simple rights to a single directory.

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 2:07 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] FE on Server for Each User

I have a customer whose parent company is requiring them to not have local
admin rights on each PC.  This causes problems when an updated FE file needs
to be automatically copied from the server to the folder on the FE.  This FE
file has not been in the folder under Documents and Settings that users do
have rights for.  Unfortunately, during this changover, a migration tool was
used, and now the user's folders under Documents and Settings have a variety
of different naming methodologies (same as before), so I can't
programmatically determine that folder's name for each user.

A suggestion has arisen to place each user's FE files on the server, with
each user having their files in a folder with their user name.  I can make
this happen programmatically, but I wonder what everyone's thoughts are on
this method.  Any pros, cons, or gotcha's?

Thanks!
Dan Waters


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

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