Skip to main content

By Netexpress 5.x we include this command to special-names

call-convention 74 is win32api.

What is to do for Visual Cobol?

Wich library must be loaded?

It is not easy to call application from cobol application, then on a 64 bis os, the application can be installed as 32bit or 64bit and the application are stored in other directrories.

What is the best way to call this programs with "winexec"?

Thanks for help

cg

By Netexpress 5.x we include this command to special-names

call-convention 74 is win32api.

What is to do for Visual Cobol?

Wich library must be loaded?

It is not easy to call application from cobol application, then on a 64 bis os, the application can be installed as 32bit or 64bit and the application are stored in other directrories.

What is the best way to call this programs with "winexec"?

Thanks for help

cg

win32api is just a user name that you assign to call-convention 74. It can be any-name. 74 indicates that you wish to link to the system .lib files. 66 would mean that you want to dynamically load the system .dlls at run-time instead of link time.

The call-convention is not specific to bitism. If you compile as 64-bit within the IDE then it will link to the 64-bit libraries and load the 64-bit system routines. The same is true for compiling from the Visual COBOL command prompt. There is a 32-bit version and a 64-bit version. They are used to setup the environment correctly to point to the correct selected bitism.

Net Express allowed compilation to 64-bit as well and it works the same way that I just described for Visual COBOL.

Terms & ConditionsAccessibility statement