Am not having any success when joining my preciously secured db, but now
unsecured, to (what I hoped to be) the company-wide security group.

Here is what I did: (not on the first try though – stumbled several times
trying to get it all sync'd up)

1.    Created a database "SecurityDB", that was connected to the system.mdw.
2.    In the "SecurityDB" database, created the company-wide securitygroup mdw
file.  Saved as "CompanySecurityGroup.mdw" in network folder.
3.    Created a password for the admin user, added a new user – NewAdmin –
added new user to the Admins group, and removed the admin user from the
Admins group.  Closed DB.
4.    Logged on as the NewAdmin and created a password.  Closed DB.
5.    Logged on as NewAdmin using new password.
6.    Using the Wizard, selected all groups assigning IDs to each group.  No
permissions for user-group.  Added one new user – Newuser1 with password and
PID (not default) – and placed in admins group.  Verified NewAdmin was also
in Admins group.  Closed DB
7.    Removed Security from database – "OlderDB" - that had its own mdw file by:
a.    Logging on as OlderDBAdmin
b.    Gave the users group full permissions on all objects
c.    Gave the Admin user full permissions
d.    Put admin user back in admins group
e.    Removed admin password
f.    Rejoined system.mdw
g.    Closed database
8.    Next, I created a new database "ImportOlderDB", connected to the
system.mdw and imported all of the objects from the "OlderDB".  Closed DB
9.    Opened "ImportOlderDB"
10.    Joined the "CompanySecurityGroup.mdw".  Closed DB
11.    Logged on as NewAdmin (using password) created in step 3.
12.    Now the issues start
a.    The "ImportOlderDB" Owner is the Admin user and cannot be changed.
b.    Cannot give NewAdmin or NewUser1 any database permissions.  Other
objects, yes, but not the database.
c.    Cannot give the Admins group or any other group any permissions on the
database.

Am extremely frustrated at this point.  

Is there anyone who can help me create one workgroup for all of the
company's Access databases, new ones, and databases that have already been
created with their own security workgroup?

I didn't have time to read through all the steps you've performed but I have
two questions:

Have you followed all the steps in the FAQ and have you tried following my
step-by-step example (links to both on my website)?  There's also a wealth
of security info on Jeff Conrad's web site (search on here for his name).
If your goal is to have one WIF for an entire company then of course you
will need to be able to log on to existing secured apps as an administrator.
You'd also need to be able to recreate your one WIF in the case of a
catastrophic failure.

Good luck.
Keith.
www.keithwilby.com

How to keep from entering an Id and password
Why have security on Backend & Frontend
Access User Level Security
MDW Bloat?
Script error while calling help documentation
Run-time error 3326 and MDW file
Application opens read-only
MDE and Mail Merging w/ Word
Locked Out! Help!
Read/Write permissions in MS Access