Kbase P126202: Using DELETE PROCEDURE to delete .w using OCX may cause eventual hang
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/10/2007 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge 10.1A
Windows NT 32 Intel/Windows 2000
SYMPTOM(s):
Application uses OCX control to process credit card transactions
OCX vendor requires that OCX control have a new instance created for each credit card transaction
Customer placed OCX on its own window and runs that window persistently
Window containing OCX is closed by using the DELETE PROCEDURE statement
Customers who process many credit card transactions are seeing application hangs
CAUSE:
Deleting the persistent procedure which contains the window with the OCX rather than applying close to the procedure (which properly destroys the window)
FIX:
Replace the DELETE PROCEDURE statement with APPLY "CLOSE" TO <Procedure_Handle>