Access 97 Workgroup and XP

[Ian]

I have an Access 97 database that uses the workgroup
facility for security. The front end of the db is on the
users desktops while the back end is on the server. This
system ran well under NT4 but we have just been upgraded
to XP. The computers now appear unable to join the
workgroup useing the Join utility.

has anyone any ideas?

 

[Chris Mills]

I take it you are talking about the security file system.mdw (possibly renamed
by you)

MS-Access has a facility to convert this file (by listing mdw as an option
when converting files). But everything I've ever read from the experts says it
is dangerous (or worse) to convert this file.

My own tests are this:
-An A97 system.mdw can be converted to later Access or used as-is.
-If the said file was ORIGINALLY converted from an A2.0 system.mda, then
conversions work to A97 but don't work thereafter.
-This has NOTHING to do with versions of Windows, it has to do with versions
of Access. If you are claiming trouble with changing Windows, then install it
again or find the file or something but do not blame Access security. Joining
a system.mdw can be done two ways, by specifying on the command line or by
using Wrkgadm.exe to join a default workgroup. Naturally, you need to use the
right one! (either program or method, whatever suits you)

What is a "Join" utility? If you mean Wrkgadm.exe then be specific.What is the
error message when you say "unable to join"? Or after you have "joined"?

There is a newsgroup microsoft.public.access.security dedicated solely to
security issues.

Chris

 

[Guest]

-----Original Message-----
I take it you are talking about the security file system.mdw (possibly renamed
by you)

MS-Access has a facility to convert this file (by listing mdw as an option
when converting files). But everything I've ever read from the experts says it
is dangerous (or worse) to convert this file.

My own tests are this:
-An A97 system.mdw can be converted to later Access or used as-is.
-If the said file was ORIGINALLY converted from an A2.0 system.mda, then
conversions work to A97 but don't work thereafter.
-This has NOTHING to do with versions of Windows, it has to do with versions
of Access. If you are claiming trouble with changing Windows, then install it
again or find the file or something but do not blame Access security. Joining
a system.mdw can be done two ways, by specifying on the command line or by
using Wrkgadm.exe to join a default workgroup. Naturally, you need to use the
right one! (either program or method, whatever suits you)

What is a "Join" utility? If you mean Wrkgadm.exe then be specific.What is the
error message when you say "unable to join"? Or after you have "joined"?

There is a newsgroup microsoft.public.access.security dedicated solely to
security issues.

Chris




.Chris

The mdw file was created along with the database, it is
not the system mdw and it was created on Access 97.

I have attempted to join the group using the wrkgadm.exe
file (Access 97) and the same file from the XP folder. In
both cases I'm told that I have successfully joined the
workgroup. This is a porky.

I did not blame access security I simply asked for
assistance, I do however believe it is a security issue
In as far as it presents a problem accessing the db.

Since this started when our IT upgraded to XP I bo
believe it may be a factor. Thank you for your help.

Ian

 

[Joan Wild]

The mdw file was created along with the database, it is
not the system mdw and it was created on Access 97.

I have attempted to join the group using the wrkgadm.exe
file (Access 97) and the same file from the XP folder.

In XP, you need to join it by opening Access XP, and going via Tools,
Security, Workgroup Administrator

 

[Chris Mills]

In XP, you need to join it by opening Access XP, and going via Tools,

Security, Workgroup Administrator

I think it's unfortunate that Microsoft keep changing procedures. I can see a
reason to update coding mechanisms (at a pinch), but this appears to have no
visible gain.

Oh well, I suppose their new programmers need to imprint themselves?

Chris

 

[Joan Wild]

I think it's unfortunate that Microsoft keep changing procedures. I
can see a reason to update coding mechanisms (at a pinch), but this
appears to have no visible gain.

I think it has to do with changes in operating systems. wrkgadm.exe was in
the windows system folder, and a lot of users don't have access to that
folder in Win2000/XP.