No, I've put my OLE testing on hold for now. Like yourself, I'm just running into too many issues with it in this release...And to be fair (due to the fact that Ruud hasn't (fully) finished COM support yet) it really doesn't make sense to try and second-guess how things "should" work or to invest a whole lot of time developing work-arounds, etc. I'm going to wait for the next beta release or whenever it is that Ruud says it's OK to start testing OLE...
As well, I do have some concerns and questions that can only be answered with the full-blown release and documentation, example...
1) Is KiXtart peeking at COM typelibs ? I find it hard to believe that it would (this goes back to your original problem) and I figure the error your getting about missing parameters has to do with some other issue. In my humble opinion, scripting languages should never do runtime checking of method calls and should only "pass-along" whatever it is that that's coded between the ()'s. Parameter conversion and validation should be handled by the Automation Server itself (IMHO).
2) How will KiXtart 2001 object cleanup (garbage collection) be performed? In the current release, it would seem that none is being performed and there is no releaseobject() function (yet). Object cleanup is an often overlooked, but vital aspect of OLE. Especially when your dealing with out-of-proc servers like office that can be left "hanging" if not properly cleaned up.
Anyway, having said all that, I'm still going to continue to play with it though
I'm *very* impressed with what's been done to date. Especially the way in which Ruud has seamlessly integrated OLE into the KiXtart language itself. No small feat to be sure and well done...
Does anyone else have any comments about the *new* OLE ?
Shawn.