This will not works and not supported from MicroFocus!

MF declare that only Netexpress 5.1 will work on Windows 10.
Can you publish what you have done to have Netexpress 5.0 on Windows 10, 32 or 64 bit, wich version of Win10?

Thanks for answer!

Yes we missed all a functional version of Netexpress 6.0 with the state of vc7.0 (without dotnet)

Just for the record, Micro Focus does not officially support Net Express 5.1 on Windows 10. The last OS that was officially supported by NX5.1 was Windows 7 and only if you had wrappack 4 or higher installed.

Although NX 5.1 may run OK under Windows 10 it is not officially tested or supported.

Visual COBOL is the sucessor product to Net Express and it should be used for development on all newer modern platforms.

Netexpress 5.0 works fine on Win10 and Win11 last edition without any problems!

This for information and it is not ok if MF refuse support on this os! It is the same netexpress version running also under Win7.

Not everybody want to use visual studio or eclipse! We need a netexpress 7.0 with the same modules for VS7.0 (without .net or eclipse)

On windows 10 we have no problems with Netexpress 5.0. On Windows 11 we were able to work around the problems by adjusting the call order of DLLs.

Hi Wolfgang,

What do you mean with "adjusting the call order of DLLs"?

Can we stay in contact to exchange our experience? Then send me a private message!
I use the same code for Win7, Win10 and now Win11!

cg

We have observed that it makes a difference when SHBrowseForFolder is called. That's why we make a dummy call to SHBrowseForFolder when the program starts to avoid problems later.

Hi Wolfgang Köhnke

We found that calls with UNC names (\\hs-xy\c$\file.* work fine, but not N:\file.*

May I ask what the dummy call you mentioned looks like when you start the program? Code ?

Many thanks for the help.

Michael

01  pfad      pic x(255) value "c:\xyz"

call winapi SHBrowseForFolderA using pfad return-code

or a little bit others...

Please take care to pass in the right information to an API, this API takes a pointer to a structure called BROWSERINFO which contains pointers/function pointers.   

Any API may crash or cause stack corruption if you pass junk into it.   

In this example, you end up creating pointer in the structure that has the hex value 0x20202020 due to pfad containing spaces.

PIDLIST_ABSOLUTE SHBrowseForFolderA( [in] LPBROWSEINFOA lpbi );

Thanks, this can be read by microsoft, but now the code in MF-Cobol!

Thanks for your great help!