Using BUFFER parameters on a table in a PROTECTED TEMP-TABLE or DATASET in a sub-class causes error 566.

Using BUFFER parameters on a table in a protected temp-table or dataset in a sub-class causes error 566 when instantiating the instance. <Class Name> Unable to find shared buffer for <table name>.(566)

Jan 20, 2016
Knowledge

Title

URL Name

Defining-a-BUFFER-parameter-for-a-protected-temp-table-in-a-sub-class-causes-inconsistent-errors-and-stack-dumps

Article Number

000174058

Environment

Product: OpenEdge Version: 11.x OS: All supported platforms Other: OOABL

Question/Problem Description

Using BUFFER parameters on a table in a protected temp-table or dataset in a sub-class raises error 566.

Steps to Reproduce

Clarifying Information

See the following test case:

Preparation:
1. Base class:

CLASS Base:
DEFINE PROTECTED TEMP-TABLE ttCustomer NO-UNDO
FIELD custNum AS INTEGER
FIELD custName AS CHARACTER
INDEX custNum IS PRIMARY UNIQUE custnum.
END CLASS.

2. Test caller routine (test.p):

DEFINE VARIABLE obj AS SubClass NO-UNDO.

obj = NEW SubClass().

MESSAGE obj VIEW-AS ALERT-BOX.

obj:TestIt().

CATCH e AS Progress.Lang.Error :
   MESSAGE "ERROR Intercepted" SKIP
   "Number of messages:" e:NumMessages SKIP
   e:GetMessage(1)
VIEW-AS ALERT-BOX.
END CATCH.

Test Case:
1. Create the sub class:

CLASS SubClass INHERITS Base:
METHOD PUBLIC VOID TestIt ():
/*TestA(BUFFER ttCustomer).*/
END METHOD.

METHOD PRIVATE VOID TestA (BUFFER ttCustomer FOR ttCustomer):
  DEFINE BUFFER bCust FOR ttCustomer.
MESSAGE "TestA" VIEW-AS ALERT-BOX.
       RETURN.
   END METHOD .

  METHOD PRIVATE VOID TestB (BUFFER ttCustomer FOR ttCustomer):
END METHOD .
END CLASS.

2. Run test.p

Result: Failure with error 566 when executing "obj = NEW SubClass()." in test.p

Error Message

<Class Name> Unable to find shared buffer for <table name>.(566)

Defect Number

Defect PSC00338697

Enhancement Number

Cause

After defect PSC00325845 (see article BUFFER parameter for a PROTECTED TEMP-TABLE or DATASET in a sub-class causes a session crash.) was fixed, further issues were found where the AVM failed to find the correct temp-table instance.

This happens when all of the buffers use the same name.
- Temp-table ttCustomer in Base
- Default buffer ttCustomer for temp-table ttCustomer
- Buffer parameter ttCustomer for temp-table ttCustomer in method TestA
- Buffer parameter ttCustomer for temp table ttCustomer in method TestB

Resolution

Until the fix is available, use the workaround below.

Workaround

Change the name for the parameters (in either method):

METHOD PRIVATE VOID TestA (BUFFER ttpb FOR ttCustomer)
and / or
METHOD PRIVATE VOID TestB (BUFFER ttpb FOR ttCustomer)

They can share the same name as long as it is not the default buffer from the Base class.

Notes

Progress Article(s):
BUFFER parameter for a PROTECTED TEMP-TABLE or DATASET in a sub-class causes a session crash.

Keyword Phrase

Last Modified Date

11/20/2020 7:25 AM

Using BUFFER parameters on a table in a PROTECTED TEMP-TABLE or DATASET in a sub-class causes error 566.

Files(0)

Was this article helpful?

Was this article helpful?

Using BUFFER parameters on a table in a PROTECTED TEMP-TABLE or DATASET in a sub-class causes error 566.

Information

Related Articles