: The specific function you are trying to call might not exist in the version of the OLE object currently installed, or the external server (like Excel or Word) may have crashed or "died" during the call.
: 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. 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 : The specific function you are trying to
: Use the Windows Command Prompt (as Administrator) to manually register necessary components using the regsvr32 command. Example: regsvr32 MSCOMCT2.ocx Debugging with pbdebug : Use the Windows Command
: 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.
: If the app works in your development environment but fails after deployment, ensure all runtime DLLs and supporting files are included in the application folder or the system path.
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
