To understand why this error occurs, it is essential to look at how PowerBuilder interacts with external entities like Microsoft Excel, Word, Adobe Acrobat, custom .NET COM DLLs, or ActiveX components ( .ocx / .vbx files).
Use TRY-CATCH blocks to capture OLERuntimeError exceptions. This allows you to inspect the Description property for more specific details about why the call failed .
Copy critical files like pbvm.dll , pbdwe.dll , and any database driver DLLs (like pbodb.dll ) into the application folder.
Ensure that the exact runtime version used to compile the application matches the runtime version installed on the client machine. powerbuilder application execution error r0035
Copy the application EXE and all required PBD/DLL files into a single folder on a clean test machine. If it works, the issue is environmental.
Ensure the runtime files on the client machine perfectly match the build version of your PowerBuilder development environment. Locate the application executable.
In PowerBuilder, the library list is stored inside the EXE at compile time. If the developer compiled the EXE with absolute paths (e.g., C:\Projects\MyApp\libs\data.pbd ), but the application is deployed to D:\Apps\MyApp\libs\data.pbd , the runtime won’t find it. To understand why this error occurs, it is
To avoid encountering the PowerBuilder Application Execution Error R0035 in the future, follow these best practices:
This is a generic, low-level error indicating that the application attempted to perform an invalid operation at the system level. It is often the "catch-all" error when PowerBuilder encounters an issue it doesn't have a specific error code for.
If the external object's software was updated on the client machine, its public interface (API) might have changed. If a function signature was modified, renamed, or deprecated in the new version, PowerBuilder will look for the old method definition, fail to find it, and trigger the runtime error. 4. Invalid or Incompatible Arguments Copy critical files like pbvm
PowerBuilder applications often rely on external C/C++ DLLs or PowerBuilder Native Interface (PBNI) extensions. If there is a mismatch in data types, calling conventions (e.g., STDCALL vs. CDECL ), or bitness (32-bit vs. 64-bit), the external function can corrupt the application stack. 4. Windows Compatibility and DEP
PowerBuilder applications rely heavily on specific dynamic link libraries (DLLs) like pbvm.dll , pbdwe.dll , and pbshr.dll . If the client machine has a different version of these DLLs than the version used to compile the application, the system will crash with an R0035 error. 2. Corrupted PowerBuilder Dynamic Libraries (PBDs)
