Im currently using uls, and would like to be able to:

1) log the users activity by using their user level security identitys to
map out their daily work and data entry.

2) Show the current users logged into the database by using the uls.

3) Also be able run an update query based upon their user level security
idenitys. So that when they login in under their un and id their production
will be there for them to work.

1) What do you mean, to "map out their daily work and data entry"?

2) Just display a text box with its controlsource set to:
=CurrentUser()

3) Ouch! You do not need (and should not use) an update query for that.
Instead, have a field in each record, which is set to the username of
the person who can work on that record. Then, in your forms & reports,
just filter for the current user.

HTH,
TC

Hi TC -

1) I mean to record what each user has entered or changed in the database,
by their user ids and place a time stamp as to when it was done.


2) Thanks i saw that i a couple of articles also.

3) Futher information. Ok, well what im doing is running a query from one
database, and updating this database, lets say for instance; its their
numbers from which they have worked either that day, day before, for the
week, ect...

But i want to be able to user their user level ids to approprately
distribute their numbers. but they can not change their number so the data
field will be set to null value, so it can not be change.

They will have a section to enter; misc work, special projects, comments.
ect...

ok but their are 50 people who have the same record,which their are a total
of 30 records for instance; accts worked, now i need to run a query from the
database their working in and update their production database, into their
individual usernames.

The production database is for auditing purposes only, mainly for numbers
per person, per area worked, ect...

Any suggestions.

I hope that gave a better example for you!


Show quoteHide quote

Wizardry wrote:
Add fields to each table for "date of last update" and "name of the
user who did the last update". Then, in the BeforeUpdate event of each
form, just store Date() into the "date of last update" field, and
CurrentUser() into the "name of the user who did the last update"
field. Naturally you'd want to choose proper names for those two
fields; perhaps LastUpdateDate and LastUpdateUser. You'd also need to
check whether BeforeUpdate fires when you add a new record; I can't
remember & I don't have Access here to check.



Sorry, I still don't understand much of that!


Ok. Maybe, instead of storing the /user/ name of the person who "owns"
each record, you could store a /group/ name instead. Then, when a user
opens a form, you would work out what /group/ that user is in, then
filter on records for that /group/. By this means, a person could work
on any record which was owned by his /group/.

Of course, a user can belong to many groups, so you'd have to have a
rule of some kind, to work out which group(s) you wanted to use,for
each user. In other words, given an arbitrary user 'x', who belongs to
groups 'a', 'b' & 'c', which of those three groups will you record as
being the "owner" of records entered by user 'x'?

HTH,
TC

Complaint about Jeff Conrad, MVP
Using http://www.jmwild.com/security97.htm Step 12 - error?
Field level security solution
How can I get my Database to Use correct workgroup file
Log users accessing the database
MS Access Web security
Another Restrict Question
"Administer" permissions removed, now stuck
Conratulation
Can you use user-level security on a linked database?