Hi, Jean-Charles -

You neglected to say what O/S version(s) you are using... I'm assuming Windows 10?

Since mscomm32.ocx is not distributed with Windows 10, I'm guessing this OCX is old and you are attempting to utilize its functionality in an operating environment it was never designed for.

A quick web search showed results that are not promising. Here is one discussion thread from MSDN:

https://social.msdn.microsoft.com/Forums/en-US/942060fc-07c2-4273-88da-0fd4d921f86b/mscomm32ocx-with-windows-10

Perhaps if you submit another question that explains what you are needing to do, someone in the community may have suggestions or recommendations. If so, please include mention of PB product version(s) and O/S version(s).

Regards. John

Hi John,

I use mscomm32 ocx in my powerbuilder (2019 or 2021) applications and it runs fine on Windows  7, 8, 10. (32 or 64 bits OS)

But it works only when I compile my app's in 32-bits . It doesn't work when I compile my app's in 64-bits ( see code generation option platform in PB Projet)

Regards,

JC

Unless you have a separate, 64-bit compatible version of mscomm32.ocx, you're going to be restricted to using the version you have in a 32-bit application, because that's the architecture the ocx was created for.

Look at sysmon.ocx, for example. On my Win10 machine, the 32-bit version of this ocx resides in the C:/Windows/SysWOW64 folder and it's size is 337,408 bytes. The 64-bit version resides in the C:/Windows/System32 folder and its size is 423,936 bytes. Two versions for the two architectures.

I suspect there might not be a 64-bit version of this particular ocx, so you'll probably have to find a different means of accessing COM ports in a 64-bit application.