Kbase 16355: Problems with Persistent Procedures and Valid-Handle
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  16/10/2008 |
|
Status: Unverified
GOAL:
Workarounds to a problem where saved handles to a procedure that has been RUN (or handles that are acquired in some other way).
FACT(s) (Environment):
Progress 8.x
CAUSE:
Handles are readily re-used when one persistent procedure is destroyed
and another created. Procedure handles are just memory pointers and, in this case, the memory is re-allocated so valid-handle returns true (it is a valid handle) although it is not referencing the same widget you thought it was.
FIX:
To fix this problem in Progress Version 7.x, you must put information in private data to ID the procedure uniquely and then test that as well as testing valid-handle.
In Version 8.x, there is a new attribute for procedure handles that retrieves the unique identifier for this instance of this procedure.