Home > Archive > Getting Started with dBASE > March 2006 > Logged in User()'s ??









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Logged in User()'s ??
Rick

2006-03-05, 8:27 pm

Hi
I have a dbase Plus 2.2 client/server application where each user is assigned a Borland user name gruop and password. Is there a way to determine the number and who is logged on at any point in time?
Thanks in advance.
Rick
Ken Mayer [dBVIPS]

2006-03-05, 8:27 pm

Rick wrote:
> Hi
> I have a dbase Plus 2.2 client/server application where each user is assigned a Borland user name gruop and password. Is there a way to determine the number and who is logged on at any point in time?
> Thanks in advance.


A "Borland user name ..."? Er? Not sure what you mean.

You might consider a routine that stores the usernames in a table when
the user logs in, and when the application shuts down, removes them ...

Ken

--
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/

*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/dbase/dBASEBook.htm
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase
Ken B

2006-03-05, 8:27 pm

> I have a dbase Plus 2.2 client/server application where each user is
> assigned a Borland user name gruop and password. Is there a way to
> determine the number and who is logged on at any point in time?

Take a look in online help for Convert or Lksys().


Les Shewchuk

2006-03-05, 8:27 pm


"Ken Mayer [dBVIPS]" < dbase@_nospam_golden
stag.net> wrote in message
news:SMj6j7fPGHA.1152@news-server...
> Rick wrote:
>
> A "Borland user name ..."? Er? Not sure what you mean.


I think it's the Group/Username/Password you get when you PROTECT a
database.

> You might consider a routine that stores the usernames in a table when the
> user logs in, and when the application shuts down, removes them ...


If you are using a windows logon, you can combine the ID() with an
authorized user/counter table. This makes thing automatic. No logging on to
the system. Either the ID() is in the applications authorized users or not.

I agree with Ken, Building your own application security table give you more
control over the application and security. You can customize the programs
behaviour (turning on/off menu option or form controls) depending on the
user.

Les Shewchuk


Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com