TD-24054,TD-22634: Late bound in dynamic created column TD 6.3.9 Build 52199 even 7.0.2 Build 51869

[Acclaro]

Hello,

I try to create columns dynamically in table windows.
Therefore I created a general window class with the attributes and a column class for each datatype (because of missing datatype parameter in SalTblCreateColumnFromClass).
To set individuall attributes there are differnt functions clled by late bound to overwrite the base attributes.
This results in the error "Unable to locate corretc late bound function, should use fully qualified late bound call".
please see sample. Any idea what's wrong?
How do I set fully qualified late bound?
I hope it's my fault and no TD error

Thanks in advance
Matthias

[Michael Ehehalt]

Hi Matthias,
I got the same error today: "Unable to locate correct late bound function, should use fully qualified late bound call".
I am working with TD 7.1.1 Build 55819 and have created columns via the function SalTblCreateColumnFromClass. Is there already a solution or a workaround for the problem? Or have you found out how to set fully qualified late bounds?
Many greetings
Michael

[Acclaro]

Hi Michael,

I received the following answer (via MD Consulting)

Gupta sent me the following information.

After reviewing your bow number by the Gupta development department, your bow number TD-24054 has been closed. With the following reason:

The problem that was generated with your bug number TD-24054 is already registered with the bug number TD-22634. Gupta's development department tried to fix this bug in the past, but the fix caused many other bugs. That's why the fix was rolled back.

Gupta suggests that SalTblCreateColumnFromClass should only be used to create a column using a class as a template (i.e., to separate the UI from it).
But it is not programmatically inherited from this class.
I'm sorry I can't provide a fix here.

If you have any further comments on this ticket, please let me know. If I don't get any feedback on this from you, I'll close this ticket.

The original OT answer is my previous favorite: "... too hard to fix, ticket will be closed ..."

Up to version 7.1.2 the dynamic column also works in connection with MTable with a few tricks. With all of the following versions there are only crashes.
We can exchange information directly. Contact details are on acclaro.de

Matthias

[Michael Ehehalt]

Hi,

I'm building a form with child table and a dynamic number of columns (but max. 20). The problem occurred during the construction of a prototype. Thus, I will now go another way, since the information that it is "... too hard to fix, ticket will be closed ..." (my favorite too) suggests, that the use of late bounds in dynamic columns will not a solution for the near future ...

Thank you for the clarifying information. It saved me a lot of time.

Best regards

Michael

[Giorgio Bravi]

One of the most interesting features of the latest releases vanished in this way ...

[Acclaro]

a way of solving a problem, the best is not always chosen.
Since LateBound no longer works for dyn. columns the topic can be closed