By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,396 Members | 1,444 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,396 IT Pros & Developers. It's quick & easy.

Multiuser access and storing user objects

P: n/a
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.

May 16 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
"jofo" <jo********@gmail.com> wrote in message
news:11**********************@v46g2000cwv.googlegr oups.com...
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.


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
May 16 '06 #2

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

May 16 '06 #3

P: n/a
Thanks guys.

May 16 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.