I was in the process of selecting checks for printing when I for
unknown reasons was kicked out of vantage. Now when I try to get
into that group again it says that it is in use by me, but it is not,
so I cannot get into it. Has anyone come up with any tricks on how
to fix this? I have run into that problem with labor entry and if I
just add a new date and then delete it, it fixes the problem. That
however doesn't work in this situation. We are on 6.0.
Have you ended your old "ghost" session using ProMon? The locking message should give you the session ID of your "old" session so you can know which one to kill (or exit from Vantage and kill all with your name).
-Todd C.
-----Original Message-----
From: jackiemotz [mailto:jack@...]
Sent: Wednesday, March 17, 2004 10:51 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Locked out
I was in the process of selecting checks for printing when I for
unknown reasons was kicked out of vantage. Now when I try to get
into that group again it says that it is in use by me, but it is not,
so I cannot get into it. Has anyone come up with any tricks on how
to fix this? I have run into that problem with labor entry and if I
just add a new date and then delete it, it fixes the problem. That
however doesn't work in this situation. We are on 6.0.
Eventually Progress should release the records for update. This can take some time, however.
If you start and stop the Vantage database, the records should be released immediately.
Rick Lane, CIERP
Intelligent Systems Integration, Inc.
600 Weber Drive
Wadsworth, OH 44281
PH: 330-335-5291
FX: 330-335-7275
www.intelligentsi.com
"Helping Business Make Intelligent Use of Technology"
-----Original Message-----
From: jackiemotz [mailto:jack@...]
Sent: Wednesday, March 17, 2004 11:51 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Locked out
I was in the process of selecting checks for printing when I for
unknown reasons was kicked out of vantage. Now when I try to get
into that group again it says that it is in use by me, but it is not,
so I cannot get into it. Has anyone come up with any tricks on how
to fix this? I have run into that problem with labor entry and if I
just add a new date and then delete it, it fixes the problem. That
however doesn't work in this situation. We are on 6.0.