Skip to main content

We have a report generator integrated into our COBOL application (List & Label of Combit) via a DLL. This works smoothly for years.

Now we want to realize a sequence, where the report generator send news about "Windows Messages" back to us, so that we can initiate new actions in COBOL.

Can I noticed this news about a EVENT Procedure at the window? Must this window be "modeless" and the DLL called as "thread"?

Or must I stand on a ACCEPT in COBOL (ACCEPT ... ALLOWING MESSAGES ...)?

Alternatively, you can also use callback routines for the report generator. What is it and does it work with COBOL?

Unfortunately there are no COBOL users in the forum of the report generator, who want to do so much.


Regards
Frank-Peter Clees


#WindowsMessagesandCallbackRoutines

We have a report generator integrated into our COBOL application (List & Label of Combit) via a DLL. This works smoothly for years.

Now we want to realize a sequence, where the report generator send news about "Windows Messages" back to us, so that we can initiate new actions in COBOL.

Can I noticed this news about a EVENT Procedure at the window? Must this window be "modeless" and the DLL called as "thread"?

Or must I stand on a ACCEPT in COBOL (ACCEPT ... ALLOWING MESSAGES ...)?

Alternatively, you can also use callback routines for the report generator. What is it and does it work with COBOL?

Unfortunately there are no COBOL users in the forum of the report generator, who want to do so much.


Regards
Frank-Peter Clees


#WindowsMessagesandCallbackRoutines

There is no built-in mechanism for an ACUCOBOL-GT program to provide callback functions like this. It is possible that you could write your own C function that controls this, and then which calls the COBOL function to run COBOL code.

We have a report generator integrated into our COBOL application (List & Label of Combit) via a DLL. This works smoothly for years.

Now we want to realize a sequence, where the report generator send news about "Windows Messages" back to us, so that we can initiate new actions in COBOL.

Can I noticed this news about a EVENT Procedure at the window? Must this window be "modeless" and the DLL called as "thread"?

Or must I stand on a ACCEPT in COBOL (ACCEPT ... ALLOWING MESSAGES ...)?

Alternatively, you can also use callback routines for the report generator. What is it and does it work with COBOL?

Unfortunately there are no COBOL users in the forum of the report generator, who want to do so much.


Regards
Frank-Peter Clees


#WindowsMessagesandCallbackRoutines

Thank you "DougP".

I will do so.

We have a report generator integrated into our COBOL application (List & Label of Combit) via a DLL. This works smoothly for years.

Now we want to realize a sequence, where the report generator send news about "Windows Messages" back to us, so that we can initiate new actions in COBOL.

Can I noticed this news about a EVENT Procedure at the window? Must this window be "modeless" and the DLL called as "thread"?

Or must I stand on a ACCEPT in COBOL (ACCEPT ... ALLOWING MESSAGES ...)?

Alternatively, you can also use callback routines for the report generator. What is it and does it work with COBOL?

Unfortunately there are no COBOL users in the forum of the report generator, who want to do so much.


Regards
Frank-Peter Clees


#WindowsMessagesandCallbackRoutines

Thank you "DougP".

I will do so.

Terms & ConditionsAccessibility statement