Re: Forms 4.5 LOGON function

The way we did it is to record log-in and log-out times. We then check those in the "on-logon" trigger. The way we did it is more Machiavellian though.
If we find that the last logon date/time is later than the last logout data/time
we assume the user got hung and had to reboot. It can still take SQL*Net
about 10 minutes to kill the hung session so in order to release any locks
we kill all other sessions belonging to the same user ID without discriminating.
In other words, we kill all other Oracle sessions with that user ID period.
The side effect of this is that the user cannot be logged on more than once.

Igor wrote:

> Sorry, perhaps I do not make myself clear
> I want to trap the error code so I can display
> an appropriate error message.
> > > Hi all,
> > >
> > > I am trying to limit the number of sessions
> > > per user to 1. I have decided to use a profile
> > > and assign it to my users.
> > > The problem is that the LOGON function in
> > > Forms 4.5 (Designer) Version 4.5.7.1.2 (Production)
> > > does not raise an exception so I can trap the error code.
> > >
> > > How do you get around this?
> > >
> > > Thanks in adv
> > >
> > > Igor
> > >
> >
Received on Fri Dec 25 1998 - 15:40:09 CET