Kbase P159117: Multiple errors when closing and reopening form using temp-tables
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/05/2010 |
|
Status: Verified
SYMPTOM(s):
Multiple errors when closing and reopening form using temp-tables
One or more of the following errors:
Invalid handle. Not initialized or points to a deleted object. (3135)
Error attempting to push run time parameters onto the stack. (984)
**Unable to assign UNKNOWN value to attribute <attribute> on <widget id>. (4083)
**Unable to assign UNKNOWN value to attribute FILL-MODE on BUFFER widget. (4083)
<program name> BIND modifier not allowed for cases where neither the caller nor the called TABLE or DATASET parameter <parameter-name> has been defined REFERENCE-ONLY and neither caller nor called parameter is a TABLE-HANDLE or DATASET-HANDLE. (13009)
myMethod BIND modifier not allowed for cases where neither the caller nor the called TABLE or DATASET parameter ttMyTempTable has been defined REFERENCE-ONLY and neither caller nor called parameter is a TABLE-HANDLE or DATASET-HANDLE. (13009)
SYSTEM ERROR in a .NET event handler
Exception code: C0000005 ACCESS_VIOLATION
Fault address: 10296041 01:00295041
C:\Progress\OpenEdge\bin\prow32.dll
FACT(s) (Environment):
Same code works correctly in OpenEdge 10.2A02.
Form creates and deletes ProDataSets and associated temp-tables.
ProDataSets are passed among procedures using REFERENCE-ONLY and BIND.
Windows
OpenEdge 10.2B
CHANGE:
Upgraded from OpenEdge 10.2A02 to OpenEdge 10.2B.
CAUSE:
Bug# OE00194521
CAUSE:
When deleting a reference-only temp-table in an object, it is left in an inconsistent state that causes errors or a crash when the object is later reused.
FIX:
Upgrade to OpenEdge 10.2B01 or later
As a workaround, start the client with -reusableObjects 0. This directs the AVM not to reuse any objects, which is the same behavior as OpenEdge 10.2A.