How to publish access 2007 application so users don't have access to tables and design mode

Posted on 2012-08-16
Last Modified: 2012-08-17

I have created an access 2007 application to be run on a local shared drive for approximately 10 users.  Everything is done and working fine but I would like to publish this application so that:

1. Users cannot have access to the main table where data is stored (unless provided a password)
2. Users cannot access design mode
3. The title page pops up every time the application opens ( title page has buttons which leads to all required forms)
4. Hide all forms and tables from user view.
5. Only one user is allowed to use the application at a time.  If another user tries to access the application while in use, it should be locked.

Any help would be greatly appreciated.

Question by:sarah_siu
    LVL 74

    Accepted Solution

    So you have 5 questions here?
    Just FYI   ...This site is designed for one distinct question at a time:

    For 2-4:
    a. Split the database:
    b. Create a accde file and put it on each users computer.
    c. Create a "Switchboard" Form
    d. Hide the database window:


    Author Comment

    I can split this question into 5 different questions.  I guess perhaps I'll address the "split database" first.  I've read in your links how to split the database and why we should split.  

    So just a quick summary to ensure I understand.  I pretty much link a separate encrypted database to the front end.  The standalone database will be in a shared drive where all users have access.  then the front end (forms,queries, reports, etc.) will be downloaded into the user's computer.

    In this case, does this allow for multiple user entries at a time?  

    I am looking more so for one user at a time entry...
    LVL 74

    Expert Comment

    by:Jeffrey Coachman
    <I can split this question into 5 different questions.>
    I have implicitly agreed to help you with 2,3 and 4, so you can make a new Q for #1, and a new Q for #5

    You first split the database.
    Put the Backend (BE) (the DB with the tables only) on a shared drive on a Server
    Put the Front End (FE) in a "Safe" location. (this is your "Golden/Reference" copy of the DB that you will make any modifications to), ...and to be sure, make a backup of this FE file...
    Test the Front end db
    Create the accde file (this will be the FE the users use)
    Test the accde file
    Copy the accde file to each users computer.
    Test the FE at each users computer.

    <In this case, does this allow for multiple user entries at a time?  >
    <I am looking more so for one user at a time entry...>
    Can I ask why?
    This is something to be addressed when you post your "One user at a time " question.
    If multiple computers need to access the DB (whether one at a time, or simultaneously), the DB needs to be split in this way.
    I am sure another Expert can provide you with a system to only allow one user at a time in the database.



    Author Closing Comment

    Thanks JeffCoachman.  Actually, based on the links you sent me, I am able to do what I was looking to do.  No need to split the questions.  Have a great weekend!

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    How your wiki can always stay up-to-date

    Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
    - Increase transparency
    - Onboard new hires faster
    - Access from mobile/offline

    Overview: This article:       (a) explains one principle method to cross-reference invoice items in Quickbooks®       (b) explores the reasons one might need to cross-reference invoice items       (c) provides a sample process for creating a M…
    A simple tool to export all objects of two Access files as text and compare it with Meld, a free diff tool.
    Get people started with the utilization of class modules. Class modules can be a powerful tool in Microsoft Access. They allow you to create self-contained objects that encapsulate functionality. They can easily hide the complexity of a process from…
    In Microsoft Access, learn how to use Dlookup and other domain aggregate functions and one method of specifying a string value within a string. Specify the first argument, which is the expression to be returned: Specify the second argument, which …

    760 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    12 Experts available now in Live!

    Get 1:1 Help Now