Some users have to rejoin workgroup daily, why?

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

Guest

My database and workgroup are both located in the same folder on our shared
directory. About 50 people all have access to this and open it thru a
shortcut place on their desktops. I have two people that have to rejoin the
workgroup each morning after they completely shut down their computers the
night before. Is there some type of access set up for their machines that I
need to change or another direction that I should be looking to?

Database is Access 2000 format

Thanks,
 
I am having a similar problem but not quite the same. I
have about 50 users using Access databases. The database
and the security file are on different drives. Most people
are not having a problem but some lose the connection to
the security file for no apparent reason.
1. Is there a problem having the security file and access
db on different drives.
2. Does it make a difference if I set up the shortcut with
the full path as specified in the previous post.
Thanks - Len
 
1. Is there a problem having the security file and access
db on different drives.
No.

2. Does it make a difference if I set up the shortcut with
the full path as specified in the previous post.
Click to expand...

As opposed to what? That is what you should be doing.
 
Sorry, but your description does not make much sense. Let's pick it
apart, so we can understand what is actually happening.

We have Access databases which are all connected to the same Security file
on our X:Drive.
Click to expand...

Database are not "connected to" workgroup files. If a database is
started via a shortcut, and the shortcut uses the /wrkgrp switch, then,
the database uses whatever workgroup file is identified by that /wrkgrp
switch.

A few (5 or 6) of the more than 50 users just drop their
connection including myself and I am supporting the system.
Click to expand...

Do you mean their /network/ connection, or the connection that you
think exists between the database and its workgroup file?

The system then
comes our with the message that says that is cannot find the MDB
Click to expand...
file.

When does this happen? When you double-click the startup shortcut?
Also, is the database /split/, with a "front end" version residing on
each PC, and all the data in a "back end" version on the server?

When I look at where the workgroup is pointing...
Click to expand...

Workgroup files do not point anywhere. Do you mean, when you look at
the /startup shortcut/, the /wrkgrp switch is missing, or points to the
wrong workgroup file?

it says C:\Documents and Settings etc. I then need to rejoin.
Click to expand...

What do you mean, "rejoin"? You should not be /joining/ any workgroup
file. Do you mean, that you need to re-add (or correct) the /wrkgrp
switch in the startup shortcut?

Sorry to be picky, but, it's risky trying to answer a question, if the
problem description is not very clear. Try rewording it, choosing your
terms more carefully.

HTH,
TC
 
Len, when you set up user-level security properly, you /do/ create a
new workgroup file, but you /do not/ "join" that workgroup file.
Instead, you use a /wrkgrp switch on a startup shortcut, to identify
that workgroup file. You still think (incorrectly) that an mdb file can
be "joined to" an mdw file using the workgroup administrator function.
That is really not correct.

It's impossible to get this right just by using the wizards. You need
to obtain and follow a detailed list of written instructions - adding
and omitting nothing. One possibility is the Access Security FAQ,.
often referenced on this newsgroups.

HTH,
TC
 
Offtopic spam!

Website designing is nothing to do with security in Microsoft Access.

Would anyone reading this thread using the new Google Groups, please
report that spam, via the "report abuse" button of the "show options"
panel to the right of the poster's name.

TC
 
I have recently developed the same issues as Len and Sheryl. All was well
for the last 7 years, every user's Access application was using a networked
WIF, then we upgraded to Office 2003 from 2000, all was ok, but just after a
rebuild of a crashed Novell server, a few users began losing the assigned
membership to the network WIF and their Access application was daily falling
back to a default system.mdw in "C:\Documents and
Settings\{username}\Application Data\Microsoft\Access" which is usually
postfixed with a number (ie system1.mdw). I realize a shortcut can be
created to force proper use of a WIF, however this does not work on those
users who sufer from the daily rollback and does not satisfy an answer to the
randomness to which users are affected for myself, Sheryl and Len.
 
Jason, I have re-read all the posts in this thread, including yours,
and there is still no clear & unambiguous description of what is
actually happening.

Unfortunately, terms like "losing the assigned membership to the
network WIF", and "falling back to a default system.mdw", really do not
make any sense.

I'm sure there /is/ a problem here, but we really need a better
description, from someone, before we can help.

Start by answering the following questions.

1. Is your db split into a front-end/back-end structure?
2. How many WIFs are used?
3. Where is/are those WIF(s)?
4. How many BEs are used?
5. Where is/are those BE(s)?
6. How many FEs are used?
7. Where is/are those FE(s)?
8. Is the application started by clicking a shortcut?
9. What is the exact text of that shortcut?

That is just the basic information on how your application has been
deployed. Then you need to describe /precisely/, what happens when it
all goes wrong. Please do not use terms like "loses its connection to
the workgroup file", or similar. Instead, tell us exactly what error
message occurs, and exactly what actions make that error occur.

HTH,
TC
 
Back
Top