Multi-User Runtime

I've made a very simple task management database for a client. The original scenario was like this: 20 employees would each need to track (for themselves) their project tasks. One database would be designed and made a runtime and the runtime would be deployed on all 20 workstations. Fine, no problem. Works great.

Now user Bob and user Jane say: "Unlike most of the employees here, the two of us actually share these tasks." Two people at two workstations, but one role.

How do I tweak the database (or is it just an issue of how I install it?) so that these two can both use the same database?

Note: If they can simultaneously use it, that's gravy here and I'd be happy about that, but they are OK if only one can use it at a time as long as they can each use it from their desktop.
Who is Participating?
DatabaseMX (Joe Anderson - Microsoft Access MVP)Connect With a Mentor Database ArchitectCommented:
You can 'split' the mdb into a Front End and a Back End ... see this link:
Patrick MatthewsConnect With a Mentor Commented:
Hello mcj,

MX's suggestion would enable multi-user capabilities.  Of course, if your current schema has a one-to-one
assignment of tasks to people, now you are going to need a one-to-many, and thus probably need a
junction table to hold the assignments...


DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
And you are probably going to need a UserID field also ... to delineate between users.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.