Results 1 to 4 of 4
  1. #1
    Join Date
    Apr 2007
    Location
    Big City
    Posts
    62

    Unanswered: permissions issues

    I have access database that in use daily. Only one user may work at the time.
    Is there are a way to set up permissions, so that 2 or more people may work at the same time?

    Thank you.

  2. #2
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Yes. Where are you getting stuck?

    It should be just a matter of splitting the database to a front-end / back-end and then putting the backend on the server and each user has a copy of the front-end.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  3. #3
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    Access is a multi user application.. it can talk happily to 15..30 users when using JET as its datastore, and thousands when talking to server datastores.. so getting you Access app to talk to two or more people shouldn't be a problem.

    So first off
    check that all people using the Access applciation are opening it in shared mode
    I use 2002/XP and youneed to check the setting

    tools | options | settings
    look for the 'advanced' tab
    and make sure default open mode is "shared", whilst you are at it set record locks to edited record (assuming you are using 2000 on).

    do that for every computer that uses the application... Access settings apply to the local machine, not all computers using the application.

    Next consider taking up startrekker suggestion and split the application into a backend (the data which sits on the central machine or server and handles all the data storage) and a front end (which contains all the forms, reports etc). consider deploying the front end to each individual workstation rather than on the server.. it will reduce network traffic, but it will increase the application support requirement. For 2..3 users I don't think you need to do this as a matter of urgency, but it is undoubtedly a good practise to get into. it can become a pain managing indivulaly deployed access front ends unless you use the right tools.

    you may also want to think about tracking which user did what
    you may also want to think about an audit log
    you may also want to think about redesigning the application to use unbound forms... however with say 2..5 users Im not convinced you need to address that just yet if at all

  4. #4
    Join Date
    Apr 2007
    Location
    Big City
    Posts
    62
    Thank you so much for all the suggestions you have for me. will try to work on the issues we have, mostly the database is in use for query writing, there no apps in the database. trully, it was working fine, up until permissions been changed all over the network. me and another user lost our ability to work together. so we are trying to fix the issues. thank you.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •