You can control 99% of that with "permissions" like is covered in Access Security Seminar

Some of the trickier stuff like the navigation bars and bypass blocking you might have to have a couple of versions of the database that you distribute based on if they need that extra lockdown stuff.

@ Adam, I've already got a TempVars!DevMode. It controls some environment things for a developer. I'm wondering if I should just change that to a code like 1, 2, 3, 4 for developer, administrator, power user and regular slob. It would add a lot of code complexity but eliminate the need for a host of different .accdb/e files. Anyone done it? Got a list of features you disabled programmatically for each group of users? It gets a lot more complicated with application modules (Acctg, PR), where in one module a person is a power user, but in another they are just a slob. Does the seminar cover that? I already have permissions, maybe I can integrate the user mode into that. Oh, my head is spinning.

With the security seminar you get how to control everything about forms, you get the permission "groups" and then you can control which groups have access to edit things or maybe you hide parts of the forms for some users or make buttons do different things for different user groups. Sky is really the limit there, it can become code intensive but you can control everything. It's kind of similar to how you are saying, If user is 1 then this form does this, if user is 2 then it does this etc.

Are you talking about what a user can see and edit (or not edit) or are we talking everyone gets to see ALL but only edit a specific area?

I was in the military and created a DB for Admin, Supply, Personnel, etc.

Who                  What See             What Edit
Admin                 ALL                      ALL
Supply                 Supply                 Supply
Personnel             Personnel             Personnel
Joe                      ALL                      NOTHING

@ Tom J. Yes, like that for the actual forms. I've got permissions set up for that. Even a way to hide fields for certain users.

I was thinking more along the lines of letting a "power user" be able to create their own queries, as some users love to export data and manipulate it in apps like Excel. This can be very dangerous for DB health, so it would be nice to limit such users to select queries that are snapshots. There is code in place that will bounce non-developer users out of tables, should they enter those. This requires allowing power users to get to the Access Programming Screen (APS) from the menus, which normally prevents regular users from exiting.

I'm surprised the (US?) military let you do such a thing. In my days in the Air Force, creating a base-level db would have required 15 forms in triplicate all approved at the Pentagon for a system with immense security (way beyond the abilities of Access).