Multi-User Environment

Multi-User Environment

Post by Aage Johan » Fri, 29 Aug 2003 16:09:39

Make the tables unique. Either, choose a unique name for the table (pc
name, username, whatever), or use one common table where you have an
additional field which identifies each user or session. You didn't indicate
what kind of database you use so I've no idea how to best produce unique

1. => Updating Forms in a multi-User Environment

2. Multi-user environments

Our company has an Access 2000 database, which is stored as one .mdb file on
the server. 20 + users are in the database at any given moment during office
hours. Currently, when a user request a new report design or needs a new
module created, I design/test in a copy then import the changes into the
production database by copying it to my hard drive, import the changes and
recopy back to the server. (This is all done after-hours. We are up to 25
minutes down and 55 minutes up.)

How do I change the setup so that I can make changes (i.e. replace reports
with a new design, revise forms, add fields to tables, etc.) when others are
in the database? (Currently, if I try to change or replace an existing
report during working hours, we receive a message stating that the database
is not opened exclusively and design changes will not be saved.)

I would appreciate anyone pointing me in the right direction on how to solve

3. Multi-user environment

4. RecordLocks in Multi-user Environment

5. Matching records table in a multi-user environment

6. designing with tables in a multi-user environment

7. Access 2002 behavior in a multi-user environment

8. How to refresh table(s) in multi-user environment?

9. Updating Services Packs in a multi-user environment

10. Is this technique efficient for multi-user environment?

11. Add records in multi-user environment

12. list boxes in multi-user environment?

13. Access.Lockfile.9 in a multi-user environment.

14. Using VS.NET in Multi-user environment

15. Serviced Component In a Multi-User Environment.