Older PowerBuilder versions (pre-2019) are strictly 32-bit. If you deploy to a 64-bit system and place PBDs in C:\Program Files (which redirects to C:\Program Files (x86) for 32-bit apps), path redirection can confuse the PBVM.
Ensure that files like pbvm.dll , pbdwe.dll , and atl71.dll on the client machine precisely match the build version of your IDE.
Ensure all necessary PowerBuilder runtime DLLs and the external dependency files are included in the setup package and properly installed on the client machine. Summary Checklist for R0035 Checkpoint Is the OLE Object registered? ( regsvr32 ) Path Does the external file exist in the path specified? Code Is ConnectToNewObject returning 0? System Are the DLLs 32-bit or 64-bit? (Do they match the app?) Rights Does the user have Administrator rights?
The target OLE/ActiveX control (e.g., .ocx or .vbx file) is not registered on the current machine .
Check the application’s working directory. Compare the PBDs that exist against the library list required.
The external object (e.g., an .ocx or .dll file) required by the PowerBuilder application is not present on the user's computer, or it is not registered in the Windows Registry. 2. Version Mismatch
Unlike typical coding errors (like Null Object Reference ), R0035 usually implies that PowerBuilder knows what it is trying to do but cannot complete the interaction with an outside component. The error message often includes the name of the function, the line number, and the script where the failure occurred. Common Contexts for R0035
If none of the above solutions resolve the R0035 error, it may be necessary to: