Hello all,

I am working on a multiuser access db. I want to have people login and
then store their user information in an object. I want to store the
information because it will be used in every form along with selections
made on the forms in the database.

The db will be stored on a file server and the users will access it
through their desktop version of Access 2003.

The db is a time card project. Since all projects and time entered are
specific to one user, I wanted to store their information for various
queries from different forms. I wanted to know if this senario will
store the login information of the user as a temp object in the local
copy of the opened db. I am thinking that Access 2003 will store the
temp object like a session variable while the user is connected and
then it will just be destroyed on closing their connection.

Is this a good way of solving this problem or is there better design
practices for Access?

Thanks in advance.

"jofo" <joey.foley@gmail.com> wrote in message
news:1147790448.673039.154030@v46g2000cwv.googlegr oups.com...[color=blue]
> Hello all,
>
> I am working on a multiuser access db. I want to have people login and
> then store their user information in an object. I want to store the
> information because it will be used in every form along with selections
> made on the forms in the database.
>
> The db will be stored on a file server and the users will access it
> through their desktop version of Access 2003.
>
> The db is a time card project. Since all projects and time entered are
> specific to one user, I wanted to store their information for various
> queries from different forms. I wanted to know if this senario will
> store the login information of the user as a temp object in the local
> copy of the opened db. I am thinking that Access 2003 will store the
> temp object like a session variable while the user is connected and
> then it will just be destroyed on closing their connection.
>
> Is this a good way of solving this problem or is there better design
> practices for Access?
>
> Thanks in advance.
>[/color]

If your app suffers an error of any kind then your variables will likely be
reset and therefore emptied. Better to get the user info each time it's
required at run-time.

Keith.
www.keithwilby.com

Check out the code here on how to call the username
http://www.mvps.org/access/api/api0008.htm

Thanks guys.