A table to do this sort of login logout could take the form of
UserID int (or UserName TEXT (18))
LoggedIn DateTime
You can then either insert a row when the user first connects, and delete it on clean
exit, or leave the row there and update the LoggedIn column to NULL on clean exit.
Entry code then simply checks for the existence of the user and login, and takes over
from there.
[EMAIL PROTECTED] wrote:
>
> Manuel,
>
> Did you find a way to determine if a user got "bumped out" and is now
> trying to get back in again for the "first time"? Or would you just do this
> with a warning message and delete the prior entry if the user indicates he
> abended?
>
> Dennis
> *****
>
>
> At 09:57 PM 7/3/01 -0700, you wrote:
> >Hi Mike,
> >Here is one way:
> > �Create a login table.
> > �Capture users name in rbase.dat and see if user is already logged in.
> > �Refuse the RBase session or warn the user that they are already logged
> >in.
> > �Delete user from the login table when user exits RBase.
> >
> >REQUIREMENTS:
> >Each user must have their own rbase.cfg file with a unique user name and
> >rbase.ini pointing the desired rbase.cfg file for the user.
> >Good Luck,
> >Manuel
> >
> >MJS wrote:
> >
> >> Hi all!
> >>
> >> Some of my clients have users that are "a little" impatient. �If Rbase
> >> does not come up right away, they hit the icon again (and again and
> >> again) which causes multiple sessions of Rbase to be started and
> >> continued.....which is not good for a lot of reasons). �Is there an
> >> elegant way of preventing this?
> >>
> >> Tia!
> >>
> >> Mike Sinclair
> >
> >Attachment Converted: "C:\INET32\download\md2.vcf"
> >
> Dennis Fleming
> IISCO
> http://www.TheBestCMMS.com
>
__________________________________________________________________
Get your own FREE, personal Netscape Webmail account today at
http://webmail.netscape.com/
