TD-16061: Com Crash

[rch]

We are new to Com developement(dll).

Please look at the attachment.
The client opens a MDI-Window from server1 and from this MDI window we want to open a message box from server2. At this point the application crashes.
What's wrong?

Thank you for your help.
Reinhard

[Jeff Luther]

To read in the COM_RCH_Server.app to try it, we first need: COM_RCH_Server2 1.0 Type Library.apl

[rch]

Here are the type libraries.

[Jeff Luther]

I'm getting a FALSE return on: If oCoClassSample.Create()

Is there something that needs to be registered with regsvr32?

[rch]

I registered it with the IDE (Project/Register Server).
Then I'm getting TRUE return on: oCoClassSample.Create().

[Jeff Luther]

Got it, thanks. I registered one of the them and re-registered the other and rebuild just to be sure.

I see the crash after clicking the MDI's button. And after adding a couple dbg. msg. boxes see that it is the line:

If Invoices.Create( )

which is crashing. As to what's wrong, I don't know. I just know where. I have added defect TD-16061 for this crash.

[rch]

In what version is this bug fixed?

[Jeff Luther]

TD-16061 is not fixed yet. I see it still open and on the fix = v6 SP5 list. SP4 is the next SP release, due out in a month or so, so SP5 would be after that + 6.1 release (likely). End of the year?

[Jeff Luther]

Reinhard:

I got notice from development that TD-16061 was closed "as designed." Here's what the developer wrote:

We don't support GUI objects in our COM servers. They are intended for non-GUI logic only.

I chatted with him and the intent for a COM server was that it was to be written as non-GUI code only. We recommend you read the TD PDF book called intro.pdf for an introduction to COM and related topics in TD.