Kbase P44160: Why is my database not disconnected after the DISCONNECT Statement?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/2/2009 |
|
Status: Unverified
GOAL:
Why is my database not disconnected after the DISCONNECT Statement?
GOAL:
Why DISCONNECT statement does not work
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Versions
FIX:
The actual database disconnection occurs once the procedure who launches the disconnection is completed. One way to ensure actual disconnection occurs is to split the connection, database access processing and disconnection activities into different independent external procedures:
/* Main.p: The driver procedure */
RUN Connect.p NO-ERROR.
RUN ProcessData.p NO-ERROR.
RUN DISCONNECT.p NO-ERROR.
/* Connect.p */
CONNECT Sports2000 -1.
/* ProcessData.p */
FIND FIRST Customer EXCLUSIVE-LOCK.
ASSIGN
CreditLimit = 1000.
/* Disconnect.p */
DISCONNECT Sports2000.