S
Stan Bibbs
I have created a database in Access 2000 which requires log-on, with the
security table specific to the database. When the user adds or edits a
record, I want automatically to persist the user's identity with the new or
changed record.
That means I need a means of capturing and persisting the user's log-on data
so that it can be married to the record when it is saved. I HATE using
public module level variables to provide application-wide access, for the
standard reasons.
I'm looking for a way to grab the user log-on data and persist it for the
duration of the session (until the user quits the app) so that I can tap it
to populate the user identity field when a record is created or changed.
Do I need to create a User class with the data as properties? And if so,
how do I keep the data available throughout the session as the user navigates
and performs other tasks?
security table specific to the database. When the user adds or edits a
record, I want automatically to persist the user's identity with the new or
changed record.
That means I need a means of capturing and persisting the user's log-on data
so that it can be married to the record when it is saved. I HATE using
public module level variables to provide application-wide access, for the
standard reasons.
I'm looking for a way to grab the user log-on data and persist it for the
duration of the session (until the user quits the app) so that I can tap it
to populate the user identity field when a record is created or changed.
Do I need to create a User class with the data as properties? And if so,
how do I keep the data available throughout the session as the user navigates
and performs other tasks?