Allocating records to 4 seperate users

Good Morning, my question is, can records in a table be allocated to 4 different users names so each user gets an equal share?

Example: I have 20 records that have been imported into the backend of the database, the dialler then calls the office and a user will process that client. All four users would have five records allocated.

What we are trying to achieve is that by clicking a command button the 20 records will be updated or appended with the four user’s names , which are stored in a separate table.

I have learnt that it can be done using numbers and my demo might give a clearer picture of what I am trying to achieve.

Any suggestions would be appreciated
Currently using access 2010
Regards Ypma

I would probably use a SELECT TOP x * FROM YourTable to give you the records you want, update them with user A then change user rinse and repeat.

You'll need a couple of thing to make it scale. Make x a calculation based on the initial number of records. Make the number of users a variable as well, so that if you add more people you aren't re-writing things.

Thank you Minty for your positive suggestions , I will try and implement them when I fully understand how.
Regards Bob

Ypma,

There is another viewpoint. Are your users more or less equally capable? Is there a reason to assign a problem to a specific user? (I.e. a specialist) Or are all users at the same level with the same expertise (i.e. a generalist)? Once the problem has been entered, does the client ALWAYS get instant feedback from the user or if you load a set of records for each user, does the client associated with the problem still have to wait his/her turn?

Perhaps the answer is not to pre-allocate ANY problems, but instead have a user activate a function such that when one of your users is ready for a problem, just take the next available one. Have an indicator on your "selection form" that shows the backlog. When the problem is assigned (by being TAKEN by the user), THEN it drops out of the list of pending actions and becomes a member of that user's queue. Not before.

If the implied calls are probably equal in difficulty then it hardly matters as to which user gets which problem. In queuing theory, this is the "equal problem/equal processor" case and the solution to optimize processing rate doesn't require prior assignment of problems. In fact, neither does the "unequal problems/equal processor" case, though in that case there would possibly be a difference in the number of problems (but not the work hours) performed by each "processor" (user, agent, whatever you call them.)

Just a thought on how to simplify your problem.

Break it down into three parts.
First get your users names into a recordset and loop around it.
Second get your data broken down into the number of sections equal to your number of users.
Last - combine the second bit into the first bit.

The Doc man . Thank you for you thoughts, I am not party to the why and wherefores so will copy your feedback and let management think about how they wish to proceed.

The 20 records I mentioned go into a dialler which calls the next adviser and the clients details' pop on the screen. I get the impression some leads are easier than others and there was some cherry picking go on.

Regards Ypma

Minty. Thanks again for you input I will look have a go over the weekend.

Regards Bob