Hi, Pierre -
My quick answer is "I don't know", but I suspect this issue might be a result of PB 2022 having been built using a newer version of Visual Studio or because the DLL is a 32-bit DLL.
Because I have no familiarity with this DLL, I have many questions:
Is the ktpels6.dll locally/internally developed or is it a vendor-supplied DLL?
Is it a 64-bit DLL or is it a 32-bit DLL? (If you are trying to call it from a 64-bit PB app, the DLL also must be compiled for 64-bit).
How old is it? In other words, what software/version has been used to create this DLL?
What is the source language for this DLL?
Can you verify that this DLL entry point uses the __stdcall (Windows API) argument passing protocol?
Although you have provided the source code return statement for this external function/entry point, can you please provide the function's source prototype statement?
FYI - You do not have to include the "ALIAS FOR" clause in an external function declaration in PB when the name you assign to the external function matches exactly with the name of the function within the DLL.
Best regards, John