quote:

---

Ruud,

Just been scratching my head over another COM problem ... think this has been a problem since day one ... just that its not used too often ...

This works ok (see it all the time in Excel COM) :

$object.property("parm").value = 1

but this does not work:

$object.property("parm") = 1

that is to say, a property with parms that is NOT nested ... seems to do a GET_PROPERTY first, than does a BAD PUT_PROPERTY ... again, component tested with VB/VBS and verified ok ... 4.02 has idential behavior.

-Shawn

Ruud replied:

Well, as you know, I dropped puts of default properties, so the second example will never work.

The GetProperty you are seeing is for the IDispatch interface of '.property("parm")'. The failed put occurs when KiX tries to write to '.property("parm")'.

I know VB supports this kind of code, but at the cost of the SET command. Without a SET command, there is no way to tell what you want code like this to do.

--Ruud

---

   
Const wdUserTemplatesPath = 2
Const wdWorkgroupTemplatesPath = 3

Set objWord = CreateObject("Word.Application")
Set objOptions = objWord.Options

objOptions.DefaultFilePath(wdUserTemplatesPath) = "C:\Templates"
objOptions.DefaultFilePath(wdWorkgroupTemplatesPath) = "C:\Workgroup\Templates"

objWord.Quit

  
$objWord = CreateObject("word.Application")
$objOptions = $objWord.Options
$objPath = $objOptions.DefaultFilePath
For Each $obj in $objPath
    ?   "$obj"
Next