Results 1 to 5 of 5
  1. #1
    5 Star Lounger
    Join Date
    Jan 2001
    Posts
    1,119
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Multi-User database (2000)

    In a Multi-User database for a data entry form, what are the property settings (and what are the settings) I should change to make sure the users don't have any conflict when data entering? Should record locks be set to Edited Record? etc Is there anything that I should be aware of in a Multi user database that may cause problems?

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Multi-User database (2000)

    If you set record locking to Edited Record, and a user starts to edit a record, this record will be locked for editing (not for viewing) to other users. If you display record selectors, a little lock icon will appear in the record selector for the record being edited.
    If you set record locking to None, two users can start editing the same record (in memory); if user A then saves the record (by moving to another record for instance), user B will get a message box when (s)he tries to save the record, with three options: (1) save the record, thus overwriting the changes made by A, (2) cancel the update, thus preserving the changes made by A, and (3) copy the record to the clipboard so that it can be pasted into a new record.
    (There is also an option to lock ALL records; this is not very user-friendly)

    In general, Edited Record is the best option, but if you have a database that is mostly used for viewing, with only occasional editing, None is attractive.

    For multi-user databases, it is advisable to split the database into a back end containing only tables, and a front end containing all other database objects (queries, forms, ...) with tables linked to the back end. Give each user his/her own copy of the front end. This reduces the probability of corrupted forms caused by mult-use conflict.

  3. #3
    5 Star Lounger
    Join Date
    Jan 2001
    Posts
    1,119
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Multi-User database (2000)

    When you use the database splitter, do you create the backend on a share drive? Once the backend is created where you want it, can it be moved? When you make changes to the front end, do you have to make individual changes to each persons front end or can you just send them a revised front end that they can copy and overwrite the one they have? It seems like splitting the database is more work.

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Multi-User database (2000)

    Yes, splitting the database is more work, but rebuilding a crashed database is no fun either, and the probability of a crash is considerably lower in a split design with local frontends.

    1. When you use the database splitter, you can specify where you want the backend.
    2. If you move the backend after it has been created, the links in the frontend will be broken. Use the Linked Table Manager (in Tools | Database Utilities) to re-link the tables in the frontend.
    3. When you make changes in the frontend, modify one copy, then distribute the copy to all users. Since the frontend contains no data, you can overwrite the previous version.

  5. #5
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Multi-User database (2000)

    In addition to Hans' comments, there is one issue you should be aware of with separate front-ends for each user. If a user wants to create queries or temporary tables in their front-end, they will be lost when you put out a new version of the front-end. That is unless of course you bring those objects into you new front end. Not usually a big deal, but you should know about it before you get hit with an angry user. If you want a bit more detail on splitting a database, check the tutorial on that topic on our website.
    Wendell

Posting Permissions

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