You are here: MS Access Products > UI Builder > Product Support > Split Databases

UI BuilderTM for Microsoft® AccessTM

    Deploying User-Level Menus with a Single Back-End Access Database

UI Builder - Enterprise Edition offers you the ability to offer user-level menus based on each user's NT login.  Maintaining user profiles and role-based menus can be simplified by moving key UI Builder tables from each user's local database file to a central back-end database.  Even if you don't have the Enterprise Edition of UI Builder, you can still deploy your database in a front-end/back-end configuration with the Starter and Business Editions.

1)  Create a new back-end database, or use the Microsoft Access Database Splitter utility to move tables to a new back-end database.

2)  Ensure the following tables associated with UI Builder are moved to the back-end database:

  • tblAppInfo
  • tblAppInfo_Advanced
  • tblEventLog
  • tblRoleMenu
  • tblReportQuery
  • tblSubMenu
  • usysRole
  • usysUser
  • usysUserAltRole

3)  Ensure each front-end database you have deployed to your users is linked to the back-end database tables identified above.

4)  OpenGate Software recommends you turn logging on for each of the front end databases.  This will create a persistent connection to the back end database, reducing the time needed to open tables and change between forms.

Now when you add/modify/remove users and role-based menus, the changes will be immediately available to all instances of your database application without additional effort.

   Setting up UI Builder as a multi-user solution
Deploying UI Builder as a front-end to Microsoft SQL Server or MySQL Server?  Learn How>>

Don't have UI Builder Enterprise Edition?  Order Now>>