[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


adapt process to multi user environment

Posted on 2008-11-16
Medium Priority
Last Modified: 2012-05-05
I have a single user database with a very basic shipping process:
tblPart has a ysn field for "selected" and another ysn field for "shipped".
User select parts to ship.
Then creates the shipment.
A command button executes an append query adds the parts and shipment to tblShipPart and an update query that marks the part as shipped.

I need to adapt my process to a multiuser environment. I could use some points on the adaptations I need to make.

Question by:eliwil
LVL 77

Accepted Solution

peter57r earned 2000 total points
ID: 22970007
You are going to have to change the way you select parts.
You can't use a field on the parts table for selection, if more than one user could be selecting.

There are several different approaches you could use.
A simple one would be to use a separate table to store selections (tblMyParts).
If you create a continuous form based on this table you could then have a combobox to list the parts and you could select the parts from the list.  You would use this list as the basis of your append query and update query.

However there is still an issue here because potentially every user is using the same table to store their selections.
But part of the change for multi-user is to split the database into two files, using the database splitter tool.
Once split, then  you have a shared 'backend' file called databasename_be, which contains the tables and nothing else and a 'frontend' which contains everything else.  A copy of the frontend goes on each users pc and the backend goes in a shared folder.  It is best to place a copy of the current database into the shared folder first and then do the database split.   That way, the frontend has links to the correct folder established as part of the split.

In the frontend file, before you distribute it to each user, you delete the link  to tblMyParts and import the table from the backend into the frontend.  This will mean that each user has their own copy of the table and so there is no confusions between selections from different users.

Author Comment

ID: 22972492
Precisely what I needed. Database is already split. So, this is going to be easier than I thought. Thanks.

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Instead of error trapping or hard-coding for non-updateable fields when using QODBC, let VBA automatically disable them when forms open. This way, users can view but not change the data. Part 1 explained how to use schema tables to do this. Part 2 h…
Windows Explorer lets you open cabinet (cab) files like any other folder. In VBA you can easily handle normal files and folders, but opening and indeed creating cabinet files takes a lot more - and that's you'll find here.
Look below the covers at a subform control , and the form that is inside it. Explore properties and see how easy it is to aggregate, get statistics, and synchronize results for your data. A Microsoft Access subform is used to show relevant calcul…
With just a little bit of  SQL and VBA, many doors open to cool things like synchronize a list box to display data relevant to other information on a form.  If you have never written code or looked at an SQL statement before, no problem! ...  give i…
Suggested Courses

873 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