I work for a large company and I am having trouble finding out who is logged 
on to the data base.  I do not have admin rights to the server but I do own 
the folder that the data base is located in.  This is causing me a lot of 
trouble when I am trying to backup or make changes to the data base.
-- 
clcnewtoaccess

Once I had an application in access named Appuser witch allow to check that.



"clcnewtoaccess" wrote:

> I work for a large company and I am having trouble finding out who is logged 
> on to the data base.  I do not have admin rights to the server but I do own 
> the folder that the data base is located in.  This is causing me a lot of 
> trouble when I am trying to backup or make changes to the data base.
> -- 
> clcnewtoaccess

There's one version available at http://www.mvps.org/access

Pieter

"Marco" <Marco@discussions.microsoft.com> wrote in message 
news:04175026-087D-4B83-867D-1363C475A00C@microsoft.com...
> Once I had an application in access named Appuser witch allow to check 
> that.
>
>
>
> "clcnewtoaccess" wrote:
>
>> I work for a large company and I am having trouble finding out who is 
>> logged
>> on to the data base.  I do not have admin rights to the server but I do 
>> own
>> the folder that the data base is located in.  This is causing me a lot of
>> trouble when I am trying to backup or make changes to the data base.
>> -- 
>> clcnewtoaccess 

Add a "UsageLog" table to your db. When startup form opens, append user 
timestamp "Login" record to UsageLog. When final form closes (assumes at 
least one "always open" form, hidden or visible), append a user timestamp 
"logout" to UsageLog (and delete records older than x days).

At any given time a query to the backend UsageLog should be able to tell you 
who has logged in but not out.

Can be expanded to include logging of other events like "special password 
supplied", "special access denied".

Get Network Login Name
http://mvps.org/access/api/api0008.htm

Get Machine Name
http://mvps.org/access/api/api0009.htm

-- 
HTH,
George


"clcnewtoaccess" <clcnewtoaccess@discussions.microsoft.com> wrote in message 
news:D789E8DB-DC46-4593-AD16-51BE17A78B52@microsoft.com...
>I work for a large company and I am having trouble finding out who is 
>logged
> on to the data base.  I do not have admin rights to the server but I do 
> own
> the folder that the data base is located in.  This is causing me a lot of
> trouble when I am trying to backup or make changes to the data base.
> -- 
> clcnewtoaccess 

Have any of you used The Access Workbench?  I found this through research and 
it seems to work well.  It even gives you the ability to send a message to 
the computer that is logged in to your data base.

Thanks for the help all!
-- 
clcnewtoaccess


"George Nicholson" wrote:

> Add a "UsageLog" table to your db. When startup form opens, append user 
> timestamp "Login" record to UsageLog. When final form closes (assumes at 
> least one "always open" form, hidden or visible), append a user timestamp 
> "logout" to UsageLog (and delete records older than x days).
> 
> At any given time a query to the backend UsageLog should be able to tell you 
> who has logged in but not out.
> 
> Can be expanded to include logging of other events like "special password 
> supplied", "special access denied".
> 
> Get Network Login Name
> http://mvps.org/access/api/api0008.htm
> 
> Get Machine Name
> http://mvps.org/access/api/api0009.htm
> 
> -- 
> HTH,
> George
> 
> 
> "clcnewtoaccess" <clcnewtoaccess@discussions.microsoft.com> wrote in message 
> news:D789E8DB-DC46-4593-AD16-51BE17A78B52@microsoft.com...
> >I work for a large company and I am having trouble finding out who is 
> >logged
> > on to the data base.  I do not have admin rights to the server but I do 
> > own
> > the folder that the data base is located in.  This is causing me a lot of
> > trouble when I am trying to backup or make changes to the data base.
> > -- 
> > clcnewtoaccess 
> 
> 
>