What can I put into the program to know who is logged on?

D

DDrowe

I have a program that several people are supposed to have access to. My
problem is that when it is open for long periods of time, I would like to
know by whom. Since only one person can save changes at a time, it would
help to be able to know who is tying up the program.

Thank you.
 
D

DDrowe

I have user level security through MS on the program. Each of the allowed
users has their own password to access the database. The program is located
on a corporate wide directory (Z:) and everyone has a shortcut to this main
program on their desktops.

Hope that sounds right. It seems to be working pretty well so far except
for the rouge users that open it and don't sign off when they are through.

Thanks

Joseph Meehan said:
DDrowe said:
I have a program that several people are supposed to have access to.
My problem is that when it is open for long periods of time, I would
like to know by whom. Since only one person can save changes at a
time, it would help to be able to know who is tying up the program.

Thank you.
Click to expand...

There are a number of possible solutions. I am assuming that the
database is located on a LAN. That being so each users should be accessing
it using their own Front End. The Front Ends have most everything except.
That is they would have the forms, reports and queries. The Back End (the
part on the server, only stores the information (the Tables).

This split database concept solves and prevents many problems when more
than one person needs to access data.

The next step I would recommend is user level security. However it
might be overkill for your needs. I don't really know your needs or what
they may become so I can't tell.

I suggest you start by reading
http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

Access security is a great feature, but it is, by nature a complex product
with a very steep learning curve. Properly used it offers very safe
versatile protection and control. However a simple mistake can easily lock
you out of your database, which might require the paid services of a
professional to help you get back in.

Practice on some copies to make sure you know what you are doing.
Click to expand...
 
R

Ron Hinds

You didn't mention which version of Access you are usng, but check out these
Jet database utilities:

http://support.microsoft.com/default.aspx?scid=kb;en-us;176670

The one of interest to you is called LDBUser, I believe. You point it at a
..LDB file and it will tell you the name(s) of the currently logged in
user(s).

DDrowe said:
I have user level security through MS on the program. Each of the allowed
users has their own password to access the database. The program is located
on a corporate wide directory (Z:) and everyone has a shortcut to this main
program on their desktops.

Hope that sounds right. It seems to be working pretty well so far except
for the rouge users that open it and don't sign off when they are through.

Thanks

Joseph Meehan said:
DDrowe said:
I have a program that several people are supposed to have access to.
My problem is that when it is open for long periods of time, I would
like to know by whom. Since only one person can save changes at a
time, it would help to be able to know who is tying up the program.

Thank you.
Click to expand...

There are a number of possible solutions. I am assuming that the
database is located on a LAN. That being so each users should be accessing
it using their own Front End. The Front Ends have most everything except.
That is they would have the forms, reports and queries. The Back End (the
part on the server, only stores the information (the Tables).

This split database concept solves and prevents many problems when more
than one person needs to access data.

The next step I would recommend is user level security. However it
might be overkill for your needs. I don't really know your needs or what
they may become so I can't tell.

I suggest you start by reading
http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

Access security is a great feature, but it is, by nature a complex product
with a very steep learning curve. Properly used it offers very safe
versatile protection and control. However a simple mistake can easily lock
you out of your database, which might require the paid services of a
professional to help you get back in.

Practice on some copies to make sure you know what you are doing.
Click to expand...
Click to expand...
 
Top