Logon Form

[Guest]

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?

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?

Thanks for any help!!!

 

[Keith W]

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

 

[hilarywalker]

i think you should create just one front end, that will be more convenient.

 

[Douglas J. Steele]

Yes, but each user should have his/her own copy of that one front end.

 

[Some Bloke]

i think you should create just one front end, that will be more convenient.

More convenient than recovering a corrupted data file? I think not.

 

[TC]

Sorry, that is bad advice. It is commonly believed that having many
users sharing the same font-end, significantly increases the risk of
data corruption. Each user should therefore have their own copy of the
front end.

HTH,
TC

 

[Guest]

Thanks for the advice Keith! How would I do this though? " You can deliver
front ends to users PCs by using a simple batch file." I would be doing
this via an SQL Server. Not sure if that would matter or not?

Thanks again!

 

[Douglas J. Steele]

Even if your back-end is SQL Server, your front-end is still an Access
application, or, more specifically, a single .MDB file that can be copied
like any other file.