Rick Brandt wrote:
Deano wrote: i.e the best way to have multiple validated users on the system who
can then access the back-end? Or is it just as easy to write your
own user management and login form and base your code on that?
Having multiple users and implementing User Level Security have
little to do with each other. Only if you want different users to
have different permissions to certain areas of the app does ULS
become a requirement. If you just want to track user-names (who did
what) then you can use an API function to retrieve the Windows
networking user name without bothering to sett up Access security.
I'm mainly thinking about how I write the code to allow each user to access
the data. If I use ULS does that make development easier in implementing my
locking strategy etc?
Else if I use my existing login form I can differentiate users and work out
who's doing what at any one time. I think I would prefer this as I'm set
for alot of rewriting a good solid, working single-user app over the next
few months. Access security is one step that would be nice to leave out if
it's a luxury and only really needed if I want to lock down the data in the
mdb.
I'm still horribly naive about multi-user issues so forgive me for appearing
dense.
--