[AccessD] WORKGROUP FILES

JWColby jwcolby at colbyconsulting.com
Fri Dec 8 18:28:36 CST 2006


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

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of JWColby
Sent: Friday, December 08, 2006 2:39 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] WORKGROUP FILES

Charlotte,

I didn't realize there were multiple workgroup files.  In fact I am not
absolutely certain that is the problem.  I have always, from the day I
walked in to the client, logged in as administrator.  If I needed to
troubleshoot a problem that a user was having, I went to a user's desk and
looked at it.  Now I live a thousand miles away and must remote in to
manipulate the database.

I am trying to get at data in a SQL Server database from Access.  I linked
the tables using odbc and logged in as my Admin user (of course).  I can
open the database and see the data in the tables.

USERS get an error IMMEDIATELY when they open the database.  I think it is
because of code that is trying to set up access to these tables, but I can't
be sure because I am not there. So...

I asked the client to set me up a "regular user" (jwcolby) on my normal
desktop machine (which is now locked away on a shelf in the server room,
serving just me for remote access).  My user can not even open a BE, FE,
library, NOTHING.  I get an error message "The Microsoft Jet Engine cannot
open the file c:\yadayada.  It is already opened exclusively by another user
or you need permission to view its data".  I can build blank databases just
fine with the new jwcolby user.

Sounds like an MDW/workgroup problem to me.

So... I am trying to determine what workgroup file is being used by the
ADMINISTRATOR user, where it is located, and how to join that workgroup by
the jwcolby user that is being denied access to everything.

Is that clear?

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 Charlotte Foust
Sent: Friday, December 08, 2006 5:10 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] WORKGROUP FILES

John, I don't understand what you're saying.  Are you having trouble
accessing Access tables *through Sequel Server* or logging into SQL server,
or logging into Access??  And why, oh why, are there multiple workgroups
like that for different users? Or is it multiple workgroups for different
databases?

Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of JWColby
Sent: Friday, December 08, 2006 12:38 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] WORKGROUP FILES

I still need help figuring out what workgroup file a user belongs to and how
to join a different workgroup.  I am trying to test problems connecting to a
SQL Server source at my client.  My admin user can connect, users can't.  Si
I had them create me a "user" on my desktop that I can log into rather
logging in as the admin.  That works, but when I try to open any access
database, I get an error "database in use or no permissions" or something
similar.  It sure looks like an MDW problem, but I just can't figure out how
I discover the physical location of the mdw file that the admin user belongs
to, and then how to cause my new "user" to join that workgroup.  
 
John W. Colby
Colby Consulting
www.ColbyConsulting.com
 
--
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

--
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




More information about the AccessD mailing list