Changing MS Login ID on-the-fly?

I'm building an app that isn't exactly Fort Knox security-wise.

People who use it fall into three categories:

Those that are in a table and have "Edit" permission.
Those that are in the same table and have "Admin" permission
Those that are not in the table at all and have "Browse" permission.

Right now, I'm just casing out on the permission and
enabling/disabling buttons/controls based on permission in each
Form_Open() routine.

I know I can disable F11=>Database Window, but the brass ring would be
to make it more challenging for somebody to directly edit a table by
somehow getting the Database window open or, for that matter, just
doubleclicking on the back end from Windows Explorer.

To that end, I'd like to apply MS Access security "under the table"
so-to-speak.

I'd set security on all tables, but only for three MS Access UserID's:
ReadOnly, Edit, and Admin.

Then, when somebody logged on, I'd trap their LAN UserID; look it up
in the "People" table; case out on the permission level; and log them
in as MS Access UserID ReadOnly, Edit, or Admin.

Is this possible to do? Seems like there may be a chicken-and-egg
conundrum here...

No, you can't change the login USERID after the login. Sorry. Not, at least,
with standard Access or any system API calls that I know about.

Larry Linson
Microsoft Access MVP

"PeteCresswell" <GoogleGroups@FatBelly.com> wrote in message
news:74d79443.0312261238.223d99d3@posting.google.c om...[color=blue]
> I'm building an app that isn't exactly Fort Knox security-wise.
>
> People who use it fall into three categories:
>
> Those that are in a table and have "Edit" permission.
> Those that are in the same table and have "Admin" permission
> Those that are not in the table at all and have "Browse" permission.
>
> Right now, I'm just casing out on the permission and
> enabling/disabling buttons/controls based on permission in each
> Form_Open() routine.
>
> I know I can disable F11=>Database Window, but the brass ring would be
> to make it more challenging for somebody to directly edit a table by
> somehow getting the Database window open or, for that matter, just
> doubleclicking on the back end from Windows Explorer.
>
> To that end, I'd like to apply MS Access security "under the table"
> so-to-speak.
>
> I'd set security on all tables, but only for three MS Access UserID's:
> ReadOnly, Edit, and Admin.
>
> Then, when somebody logged on, I'd trap their LAN UserID; look it up
> in the "People" table; case out on the permission level; and log them
> in as MS Access UserID ReadOnly, Edit, or Admin.
>
> Is this possible to do? Seems like there may be a chicken-and-egg
> conundrum here...[/color]