System.MDW interchangeable??

[JRF]

Is the system.mdw interchangeable between versions of Access for example,
Access 97 and Access 2000 and Access 2003?

Could the system.mdw file installed with Access 2003 be copied into the path
for launching an Access 97 application?

 

[Rick Brandt]

Is the system.mdw interchangeable between versions of Access for example,
Access 97 and Access 2000 and Access 2003?

Could the system.mdw file installed with Access 2003 be copied into the path
for launching an Access 97 application?

Newer Access versions can use an older version MDW. I don't believe the
reverse is true though.

 

[JRF]

Not having a copy of Access 97 with me, is there a generic version of the
file that can be interchanged into the default location on a computer which
the secured applications reside. I am going to attempt dropping all the
workgroup features on an existing machine, where the computer owner
overwrote the system.mdw file with a bunch of security, no backup was made.
Or, does the system.mdw file become specific with each installation on a
particular machine. Only one copy of Access is loaded on a server, and all
users have a shortcut that points to the Access 97 folder on the server and
the database applications. I just want something to fall back on, even
though I will make a copy of the existing *.mdw file before de-securing the
applications.

 

[TC]

Not sure if this helps, but - your best bet always is to write down on
paper, the case-sensitive info that you use to create the workgroup file:
Company name, Organization name, Workgroup ID (WID), user/group names &
PIDs. Then you can always create a new workgroup file, from scratch, with
any old or new version of Access, and get a working result. This avoids the
possible bad effects of old/new version inconsistencies, loss of previous
workgroup file(s), & so on. IMO the key thing with workgroup files is to

write the info. down on paper<, rather than just relying on copies of the

physical file(s).

HTH,
TC