Please allow me to set expectations: The Q&A forum is NOT a support site - We volunteer our spare time and limited expertise to answer technical questions related to Appeon products only because we want to help. We do NOT provide live problem resolution via Teams or similar tools. If you feel you require support by Appeon, you have the option of opening a Premium Support issue (not free). More info here: https://www.appeon.com/premium-support.html

If you wish to continue here in the Q&A forum with advice regarding how to interface a PB application with an external DLL, you really should provide the following: (1) The bitness (32 or 64) of your PB application. (2) Are you having issues running the app from within the PB IDE or when it is a compiled/deployed app? (3) The details/specs of the DLL functions... entry point name, number of arguments, argument data types, how is each argument to be passed (by value, by reference, or readonly) the return data type, is character/string data to be ANSI or Unicode16LE encoded, etc. (4) PB can interface with external DLL's only when the DLL uses the _stdcall (also known as the WinAPI) calling convention. (5) If structures are being passed, what are the data types of the structure members and what packing alignment (default: 8-byte, 1-byte is optionally available) is expected by the DLL. The path to any DLL to be called by a PB app must be located in the app's execution path.

Last but not least, we are PB people here, not Tuxedo people, so we likely will not have any knowledge of Tuxedo, what it is or what it does, so please keep this in mind. Help us help you by giving us as much information as you can.