Currently, when a user logs in, I open an unbound, hidden form, and write their profile info (from a table using their login name) to that form (frmUser). I then refer to that form on numerous pages to customize the view and edit/delete/add authorities. I did this because it seems a lot quicker to look up in a form than using dlookup to tblUserProfile.
Is there a better way?
I've thought about creating a set of two local (front end) tables with this info, in lieu of an unbound form.
I think I recall somewhere about tracking properties in VB. I have no idea how that works.
Adam
Denver, CO
__._,_.___
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (1) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar