Execution Error R0035 — Powerbuilder Application

: Wrap your OLE calls in a TRY-CATCH block. Catching the OLERuntimeError exception allows you to inspect the "Description" property, which often provides more specific details about why the call failed.

The is a common runtime issue that typically surfaces when a PowerBuilder application fails to call a function on an external OLE (Object Linking and Embedding) object. Unlike standard coding errors that appear during compilation, R0035 occurs while the application is running, often because a required external component—like a DLL, OCX, or an automation server—is missing, corrupted, or not properly registered on the target machine. Common Causes of Error R0035

: Ensure that the external application (e.g., Microsoft Word, Excel, or a custom VB application) is installed and functional on the machine where the error occurs. powerbuilder application execution error r0035

: In PowerBuilder, use the OLE Browser (found under Tools -> Browser -> OLE tab) to verify that the properties and functions you are calling actually exist in the registered object. Debugging with pbdebug

: Moving an application to a new virtual machine or a different OS (e.g., Windows 10 to Windows 11) can break OLE connections if the supporting libraries are not present. : Wrap your OLE calls in a TRY-CATCH block

: The most frequent culprit is a missing or unregistered .ocx or .dll file required by the OLE object.

Are you seeing this error with a specific like Excel or Crystal Reports, or does it happen when your application first launches ? PowerBuilder Application Execution Error R0035! Debugging with pbdebug : Moving an application to

: Upgrading to newer versions of tools like Crystal Reports without updating the corresponding OLE connection logic can trigger this error. How to Fix PowerBuilder Error R0035