Gary Kjos
garykjos at gmail.com
Mon Dec 11 09:25:24 CST 2006
I'd guess there is probably a Sarbanes-Oxley Administrator involvement in this change. GK On 12/11/06, JWColby <jwcolby at colbyconsulting.com> wrote: > It does look like the problem is a rights issue to the folders. I tested > this morning and the user has read-only rights everywhere and gets an error > when I try to change to read-write. > > 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 JWColby > Sent: Friday, December 08, 2006 7:29 PM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] WORKGROUP FILES > > I'll check that. > > > 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 Jim Lawrence > Sent: Friday, December 08, 2006 6:26 PM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] WORKGROUP FILES > > Hi John: > > If that is the case it would appear that the users have limited access to > the directories where either the security file, databases or lock-file > resides. This is not a problem with Access but a problem with how the > permissions on directories themselves are setup.... this is an IT issue and > nothing to do with you. All the respective directories must have read and > write access for all users. > > Jim > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- Gary Kjos garykjos at gmail.com