Peter

Jeremy, not that I am aware of. There are various configuration files associated with PCOMM, but I did not think any of them had any impact on the OLE mechanism. I will poke around on both PC's and see if there is anything that looks suspiciously different. P.S. - Note that my original post was edited to change my original references to "CreateObject" (which is a VBS function) to the oorexx function .OLEObject~new. My apologies for using the wrong name. I've been working in parallel on a VBS version...

Jeremy, not that I am aware of. There are various configuration files associated with PCOMM, but I did not think any of them had any impact on the OLE mechanism. I will poke around on both PC's and see if there is anything that looks suspiciously different. P.S. - Note that my original post was edited to change my original references to "CreateObject" (which is a VBS function) to the oorexx function .OLEObject~new. My apologies for using the wrong name. I've been working in parallel on a VBS version...

Jeremy, not that I am aware of. There are various configuration files associated with PCOMM, but I did not think any of them had any impact on the OLE mechanism. I will poke around on both PC's and see if there is anything that looks suspiciously different. P.S. - Note that my original post was edited to change "CreatObject" (which is a VBS function" to the oorexx function .OLEObject~new. My apologies for using the wrong name. I've been working in parallel on a VBS version of this code and got a...

Jeremy, not that I am aware of. There are various configuration files associated with PCOMM, but I did not think any of them had any impact on the OLE mechanism. I will poke around on both PC's and see if there is anything that looks suspiciously different.

I have an error condition I cannot figure out how to solve. On one PC I issue a .OLEObject~new call for one of the IBM PCOMM OLE classes and it works every time. On a second PC with the same version of PCOMM installed (V14 if it matters) the same .OLEObject~new call never works. Error messages are pasted below. I have used Rony's program listprogids.rex to list the PCOMM classes on both PC's and they are all there on each machine according to that program. Both PC's are Windows 10 with oorexx V5.0.0...

I have an error condition I cannot figure out how to solve. On one PC I issue a CreateObject call for one of the IBM PCOMM OLE classes and it works every time. On a second PC with the same version of PCOMM installed (V14 if it matters) the same CreateObject call never works. Error messages are pasted below. I have used Rony's program listprogids.rex to list the PCOMM classes on both PC's and they are all there on each machine according to that program. Both PC's are Windows 10 with oorexx V5.0.0...

I wouldn't argue with you that the ooRexx "parse arg" should work consistently (i.e., least surprise) but coming from the z/OS TSO version and the frequent difficulties of using "null" arguments in that environment, I have always used the "workaround" of using either a period or an asterisk as a "null argument" placeholder, with code right after the "parse arg" and before the "null argument check" that does something like: parse arg arg1 arg2 arg3 if verify(arg1, ".*") > 0 then arg1 = "" /* And similarly...

I wouldn't argue with you that the ooRexx "parse arg" should work consistently (i.e., least surprise) but coming from the z/OS TSO version and the frequent difficulties of using "null" arguments in that environment, I have always used the "workaround" of using either a period or an asterisk as a "null argument" placeholder, with code right after the "parse arg" and before the "null argument check" that does something like: parse arg arg1 arg2 arg3 if verify(arg1, ".*") > 0 then arg1 = "" Not perfect,...