TRY // This is the line causing R0035 lole_myobj.MyFunction("Parameter1")
If you are upgrading an older PowerBuilder application (e.g., from version 8.5 to 10.5+), older OCX controls (like old Crystal Reports RDC) may not work on modern Windows 10/11 environments, as indicated in SAP support cases . You may need to upgrade the third-party control or re-engineer the code to use modern API calls. Summary Checklist for Troubleshooting R0035 Run regsvr32 on all required .ocx and .dll files. Verify 32-bit components are registered via SysWOW64 .
Errors in the syntax of the external function call in PowerScript (e.g., passing wrong parameters, calling a function that doesn't exist) can trigger this error. How to Fix PowerBuilder Error R0035
This is the most frequent cause of R0035. It usually happens when moving an application from a development machine to a user's machine.
When writing standard PowerScript code, the PowerBuilder IDE acts as a strongly-typed environment. If you misspell a function name or pass the wrong type of variable to a global function, the compiler catches the mistake immediately. powerbuilder application execution error r0035
// Later in code... if IsNull(lnv_obj) OR NOT IsValid(lnv_obj) then return lnv_obj.SomeFunction() // This would crash if not checked
In the PowerBuilder ecosystem, this error indicates a severe memory management failure. It occurs when the application attempts to read from or write to a memory address that it does not have permission to access, or an address that no longer points to a valid object.
The PowerBuilder code tries to call a method like .Open() or .ConnectToNewObject() before the object has been successfully created or connected. Solutions to Fix R0035 Follow these steps to diagnose and resolve the R0035 error. Step 1: Verify the External Object File
: 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. TRY // This is the line causing R0035 lole_myobj
: Use the SetAutomationTimeout function to lengthen the allowed wait time for OLE calls if the server is slow.
Resolving this error requires identifying the underlying trigger. The most frequent culprits include: 1. Missing or Mismatched Runtime DLLs
The .dll or .ocx file required by the application is not registered on the client machine. This often happens during deployment to a new environment.
: Wrap the call in a TRY...CATCH block for OLERuntimeError to capture more detailed information about why the call is failing without crashing the app. Verify 32-bit components are registered via SysWOW64
Check the companion DLLs in the same folder or the App Path.
[Isolate the Code Trigger] ──> [Verify Components] ──> [Audit Data Types] ──> [Implement Try-Catch] Step 1: Isolate the Faulty Object Call
PowerBuilder execution error (typically displayed as "Error calling external object function") is a runtime error that occurs when a PowerBuilder application attempts to invoke a method or property on an external object—usually an OLEObject or ActiveX control —that the system cannot find or execute. Core Causes
System-level files required by the control, such as specific Windows components (e.g., MSCOMCT2.ocx ), are missing .