Two Front-Ends - Best Practices?

[rhubarb]

I am distributing a second front-end for two managerial users that need access to a specific form that no one else should. Any caveats here? The only difference in the front-end is an additional button on the switchboard that leads to a form/subform arrangement that links to two tables (that all others will not need to access to).

[rpeare]

Just be sure that if the two copies of the database have any objects in common (forms, reports, queries, etc) that when you update one of them, you update both of them or you're going to end up with a mishmosh of stuff that will work for one user but not another depending on which version of the database they are in.

[ItsMe]

I create different FE files for different purposes. When it comes down to access of features, I typically employ user credentials, enabling/disabling or denying access. Like rpeare mentioned, it can be cumbersome keeping track of multiple versions. I will create a different version for different operations and or phases of workflow. This way it is easier to envision, in my minds eye, which FE files and which workstations need attention.

[orange]

Ditto on ItsMe and rpeare concerns. You might consider 1 FE with user credentials. If the manager with acceptable credentials logs in, then enable the buttons for ManagersOnly and disable the other button/options.
Seems a separate Login form that would open the FE and enable appropriate buttons of the menu screen/options screen.

That just keeps it to one FE(reduces maintenance worries/combinations).

Good luck with whatever you decide.