Greetings, Amit -
PowerBuilder can invoke functions in Windows and third-party DLL's that are external to PowerBuilder, using what is called an External Function Definition (EFD). An EFD is a declaration (it does not get executed) that tells the PB compiler the name of the DLL, the name of the function to be called within the DLL, the argument(s) (if any) to be passed to the DLL function, the datatype of each argument, whether each argument is passed by value or by reference, and the return value (if any) expected from the DLL function. In essence, the EFD tells PB how to call the DLL function and exchange data between it and PB. We can't help you troubleshoot this issue without this information.
Typically, the EFD is defined in the object that invokes the DLL function. Find the external function definition. Open the object (probably a window or a user object) that calls the DLL function. Open an existing function or event script in that object. Along the top of the PowerScript editor pane are three dropdown lists. Open the middle dropdown list. The last item listed in that dropdown list should show a small "notepad"-like icon if there are any EFD's defined in this object. If the icon is there, select the last item in this dropdown list to display the EFD('s). Select and Copy everything you see there and paste that into a reply here.
Now find the code that actually calls the external DLL function. Copy it and paste it into a reply so we can inspect it.
We also need the full and exact text of the error message you are receiving during execution. The error message number is not going to help us help you.
Is the DLL name actually Clipbxxx??? I cannot find any info on a DLL by that name on the web.
Find the DLL. It probably resides in the same folder as the application if it has been created by a third-party vendor or internally. From Windows Explorer, navigate to the production application's folder, right-click the DLL, go to Properties, find out as much info about the DLL (who created it, version #, create date, etc.) as you can and report back here.
Regards, John
Can you check out the dependencies of clipbxxx.dll? (you can use "dependency walker"). See if all dependencies are on the machine.
Is C++ runtime installed? Is .Net framework installed?