Random form presentation

  • Thread starter Thread starter cunger28
  • Start date Start date
C

cunger28

I need the ability to randomly present records to end users who are utilizng
the same form. I would like to avoid the possiblity of two people working
the same record at the same time...

Thanks,
 
2 suggestions:
1. Either split your database and then more than one person at a time can
use the same form.
2. Split the database and on the frontend that you load on each user's
machine, only put the forms you want them to work with.
3. (I know, i said two) Set up security and you can allow users what you
want them to have.
 
2 suggestions:
1. Either split your database and then more than one person at a time can
use the same form.
Click to expand...

That will not prevent two users from connecting to the same record in the
backend.
2. Split the database and on the frontend that you load on each user's
machine, only put the forms you want them to work with.
Ditto.

3. (I know, i said two) Set up security and you can allow users what you
want them to have.
Click to expand...

Ditto.
 
I need the ability to randomly present records to end users who are utilizng
the same form. I would like to avoid the possiblity of two people working
the same record at the same time...

Thanks,
Click to expand...

That will be tricky and unreliable. Random means random - and there could be
two users who randomly end up on the same record!

What is the nature of the data in the tables? How is it that users will "not
care" which record they're editing?

In order to do it, you'll need to use a split database
(http://www.granite.ab.ca/access/splitapp.htm); and the form will need to be
based on a query sorting the table in random order. . Put this little function
into a Module:

Public Function RndNum(vIgnore As Variant) As Double
Static bRnd As Boolean
If Not bRnd Then
'Initialize the random number generator once only
bRnd = True
Randomize
End If
RndNum = Rnd()
End Function

Then add a calculated field to your Query by typing

Shuffle: RndNum([fieldname])

in a vacant Field cell, where [fieldname] is any field in
your table - this forces Access to give a different random
number for each record. Sort the query by this field.
 
This is a callback tool used by remote office employees to do follow up calls
with customers. I have the database split, but whenever the form opens, I
would like the detail presented to the end user to randomly select a row from
my feeder table. That way, if two people were to open the database, I'd like
to avoid both of them being presented with row 1 of my table at the same if
that makes sense.
--
Chris Unger
Analyst - Tyler, TX


John W. Vinson said:
I need the ability to randomly present records to end users who are utilizng
the same form. I would like to avoid the possiblity of two people working
the same record at the same time...

Thanks,
Click to expand...

That will be tricky and unreliable. Random means random - and there could be
two users who randomly end up on the same record!

What is the nature of the data in the tables? How is it that users will "not
care" which record they're editing?

In order to do it, you'll need to use a split database
(http://www.granite.ab.ca/access/splitapp.htm); and the form will need to be
based on a query sorting the table in random order. . Put this little function
into a Module:

Public Function RndNum(vIgnore As Variant) As Double
Static bRnd As Boolean
If Not bRnd Then
'Initialize the random number generator once only
bRnd = True
Randomize
End If
RndNum = Rnd()
End Function

Then add a calculated field to your Query by typing

Shuffle: RndNum([fieldname])

in a vacant Field cell, where [fieldname] is any field in
your table - this forces Access to give a different random
number for each record. Sort the query by this field.
Click to expand...
 
This is a callback tool used by remote office employees to do follow up calls
with customers. I have the database split, but whenever the form opens, I
would like the detail presented to the end user to randomly select a row from
my feeder table. That way, if two people were to open the database, I'd like
to avoid both of them being presented with row 1 of my table at the same if
that makes sense.
Click to expand...

Does my suggestion (of basing the form on a shuffled query) help?
 
Back
Top