Re: New Problem that I need help with

jerrodklein313 wrote:
Joan,
I probablly need to clear up a few of your questions.
1. I am using the 2003 version of Acess
2. The db on my backend is a mdw. file

I can't make any sense of this. What do you mean?

3. The boxes I was refering to, when trying to join the workgroup, are
charecters, similar to those that would appear in different font
settings

Again where are you seeing this? If you want to join her computer by
default to your secure mdw, then open Access on her computer and go to
Tools, security, workgroup administrator. Click on Join and locate the
secure mdw on the server. Close Access and then try opening the secure mdb.

4. I have tried to join her, and the others to the mdw. that my db is
on, to no avail

Does the user have windows permission on the folder where the mdb and the
mdw is located? They need full permissions.

5. I can log on with her name on my computer, just not hers

Ca you see athe network folder where the files are located, when you are on
her computer (I mean just using my network places).

6. The current db that I adobted is over 6 years old and I have no
way of knowing if it were ever secured or not

Hope this helps, in order to help me.

Jerrod

"Joan Wild" wrote:

jerrodklein313 wrote:
Thank you again. You have helped me so much, as well as so many
others. We all appreciate yours, and the other regular helpers on
here, so much.

I appreciate the feedback, thank you.

So I am back in business. I am still having issues with the three
users. I did discover something unusual though. I noticed on one
persons issue, you told the person to look under the workgroup
administrator section to see what workgroup they belonged to.

Every installation requires some workgroup file (mdw); Access can't
work without one. Out of the box, it ships with a workgroup file
named system.mdw. Access uses this workgroup for all sessions. It
silently logs you in as a user named 'Admin' using this system.mdw.
Every installation of Access has the same system.mdw, and the Users
Group and the Admin User are common to all. That is why it is
important not to give any permissions or ownership to either the
Users Group or the Admin User. It is also crucial to create a new
mdw file, as this will ensure that the Admins Group is different
than the Admins Group in system.mdw.

When I did this for the user that is having an issue with the
'Admin' error message, I found the workgroup section contained a
lot of boxes.

What boxes do you mean? A computer can have many mdw files
available to it. You are always joined by default to one of them.
Normally one would keep system.mdw as the default, as that one will
be used for all Access sessions requiring no security. When you
want to launch a secure mdb, you'd use a desktop shortcut with the
/wrkgrp switch to over-ride the default (for just that session).
You could join the secure mdw as your default, but that becomes
rather tedious to keep changing the default. Desktop shortcuts are
easier.

My settings look like this: C:\Documents and
Settings\<myname>\Application Data\Microsoft\Access\System.mdw
I tried to copy and paste this into her settings in order to join
the same group as the one I belong to, obviously using her name in
the <myname> spot.

Well system.mdw on your system should be the standard one that ships
with Access. That is not likely the secure mdw you created when you
secured the mdb.

When I do all this, it says that I have successfully
joined the group. I try to reopen the db, and it says it can't find
the group. So I try to change the group mannually, and go to the
same location in the c:drive and it wont let me change it. The
unknown workgroup remains. All I have to say is Arrrggggg!!!

What version are you using? If 2002 or 2003, go to that person's
machine and just open Access (not your secure mdb). If it can't
find system.mdw, it'll create a new one. If you are using 2000, you
can copy a pristine system.mdw from some one else's computer.

You should put your secure mdw (again this isn't/shouldn't be
system.mdw on your computer) in a folder on the network that users
have full access to. Give the users a desktop shortcut with a target
like: "path to msaccess.exe" "path to mdb" /wrkgrp "path to secure
mdw on network"

I have a feeling that you didn't create a new workgroup file when you
secured. If that is the case, then your mdb is not secure at all.

--
Joan Wild
Microsoft Access MVP


.

Relevant Pages

  • Re: New Problem that I need help with
    ... The boxes I was refering to, when trying to join the workgroup, are ... I have tried to join her, and the others to the mdw. ... Every installation requires some workgroup file; ... You could join the secure mdw as your default, ...
    (microsoft.public.access.security)
  • Re: Sticking with a defined Workgroup.
    ... workgroup file called system.mdw. ... So when you 'join' your secure mdw on the server, it is now the default mdw ... My trouble is that when I distributed my secure database by putting ...
    (microsoft.public.access.security)
  • Re: Sticking with a defined Workgroup.
    ... "Joan Wild" wrote: ... workgroup file called system.mdw. ... So when you 'join' your secure mdw on the server, it is now the default mdw ...
    (microsoft.public.access.security)
  • Re: Where is workgroup manager in access 2007?
    ... it wasn't adviseable to 'join' a secure mdw. ... The workgroup administrator will not be added to 2007. ... already decided to obsolete ULS and workgroups). ...
    (microsoft.public.access.security)
  • Re: New Problem that I need help with
    ... administrator section to see what workgroup they belonged to. ... and the Users Group and the Admin User are ... You could join the secure mdw as your default, ... That is not likely the secure mdw you created when you secured the ...
    (microsoft.public.access.security)
Loading