Re: Logon Form

Tech-Archive recommends: Fix windows errors by optimizing your registry

"naiveprogrammer" <naiveprogrammer@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:765DA0C1-F2DA-4CCA-83A4-3588599876C2@xxxxxxxxxxxxxxxx
>I have a DB that will have around 25 different users. My first question is
> should I create 25 different front ends or just one? I'm not sure if how
> it
> would affect the DB if that many people had the DB open at the same time?

Yes, all users should have their own local copy of the Front End. I don't
think you'll have a problem with 25 concurrent users unless they are
"intensive" users who are all changing data all of the time (unlikely I
would have thought). You can deliver front ends to users PCs by using a
simple batch file. It's a method I use all the time and it works well,
ensuring that users always get the latest version of the FE when they launch
the app.

>
> My second question is- I want to create a user security but I'm find the
> wizard in Access rather confusing. I basically just want a login form
> that
> the info is recorded in a table with the time that the person login at.
> Is
> this possible?
>

Yes it is but if you find the wizard confusing then it might be time to step
back and decide if you really have a requirement for this because learning
about user-level security (ULS) is far from being a trivial task. Take a
look at the MS FAQ on the subject (link on my web site). It depends how
deep you want to get into it but to implement and support ULS security
correctly you would need to be prepared to take the time to study this
document. Recording users' logging in/out habits does not come off the
shelf with ULS either, you would have to programme this into your app.

Sorry I don't have a quick fix for you!

Regards,
Keith.
www.keithwilby.com


.

Relevant Pages

  • Re: Passwords To Identify Users And Populate date/timestamp
    ... Thanks, Jeff, I will go through it and see what I can do. ... yrs. Used to go to Bend occasionally to go the the shooting range about 20 ... > Implementing Access User Level Security *IS* a complicated process ... Once you understand ULS it becomes a very valuable tool ...
    (microsoft.public.access.formscoding)
  • Re: Passwords To Identify Users And Populate date/timestamp
    ... Implementing Access User Level Security (ULS) *IS* a complicated process ... "You are about to modify the system workgroup file. ... > impossible for them to do anything that is not in my App. ...
    (microsoft.public.access.formscoding)
  • Re: Adv/disadv of using Access built-in security tools vs build in
    ... Q-Built recommends "homegrown methods" for Access security, ... about the built-in ULS and, more directly, from the fact that John ... my security needs for this project are low. ...
    (microsoft.public.access.security)
  • Re: Impossible to secure an access Db
    ... user level security, then use RWOP queries, etc., which I did. ... AND THAT ULS ONLY WORKS IF THE USERS ... Rick Brandt, Microsoft Access MVP ...
    (microsoft.public.access.security)
  • Re: Adv/disadv of using Access built-in security tools vs build in
    ... about the built-in ULS and, more directly, from the fact that John Viescas' ... my security needs for this project are low. ... See http://www.QBuilt.com for all your database needs. ... "MS wizards" are often spurned because they DO NOT a1) always work as ...
    (microsoft.public.access.security)