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

Acc2003: Best way to persist login data for multi-user app?

P: n/a
Hi All,

I'm returning to coding in Access after a break of about 4 years, and
designing a multi-user app split between a front end mdb for forms /
code etc and a backend mdb for tables.

I'm curious about how others persist information such as login IDs etc
while each user is logged in. Previously I've used a hidden form with
text fields on it to keep this information persisted, but I'm wondering
if anyone would suggest other methods?

Many thanks in advance,

Much warmth,

planetthoughtful

---
"Lost in thought"
http://www.planetthoughtful.org

Mar 16 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a

"planetthoughtful" <pl**************@gmail.com> wrote in message
news:11**********************@z34g2000cwc.googlegr oups.com...
Hi All,

I'm returning to coding in Access after a break of about 4 years, and
designing a multi-user app split between a front end mdb for forms /
code etc and a backend mdb for tables.

I'm curious about how others persist information such as login IDs etc
while each user is logged in. Previously I've used a hidden form with
text fields on it to keep this information persisted, but I'm wondering
if anyone would suggest other methods?

Many thanks in advance,


What do you have, some sort of home-grown login system? If so then yeah either
a hidden form, a class module, or global variables would all do the job. Those
are listed in the order of volatility. Hidden forms seem to be the method least
likely to lose the data due to a runtime error or other such hiccup.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Mar 16 '06 #2

P: n/a

"Rick Brandt" <ri*********@hotmail.com> wrote
What do you have, some sort of home-grown
login system?


I feel compelled to mention that, if Rick is correct about this, homegrown
login systems are easy for an experienced user to crack, so you shouldn't
count on them to protect much of anything.

Don't count on even Access' "labrynthine*" security to protect anything that
is worth US$150 to someone who wants it -- that's what very capable cracker
software, oops, I mean "password recovery software" sells for over the
Internet. I haven't tried any lately, but a few years back, I tried the
"free trial" version that was limited to 3-character passwords and it worked
just-fine-thankee.

* as characterized by Roger Jennings in his
"Access 2 Developer's Guide" and it hasn't
gotten any less "twisty" since

That said, if all you are trying to do is to keep users from stumbling over
their own fingers, it may be all you need. If that is the case, you might
want to look at http://www.mvps.org/access/api/api0008.htm for code to use
the Windows API to get the user's network login name, so the user does not
have to enter anything... just open the database application and start work.

For "persisting" (it always grates on me to see "persist" used as a verb)
user or system information over a longer period and across logouts and
relogins, I use a combination of tables in the shared tables database and in
the front end databases on each user's machine. Seems to me I put an article
on that subject up on http://accdevel.tripod.com.

Larry Linson
Microsoft Access MVP
Mar 16 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.