P.S. I'm only working with NT 4.0 right now.

Thanks

How you making out with this one ?

I did a little digging into using OLE to do this and was dismayed to find that one cannot use OLE to extract/insert macro's from one template to another... you can load them into a document and you can invoke them, but you can't move them around (?).

Have you found another solution ?

Shawn.

I know that in Access you can programatically make a module and add code to it. So maybe I should be looking down that path. But...I'd have to change the module into a macro. Don't know about that one. Anyhow, If you have some other ideas let me know.

Shawn.

excuse me if i'm using the wrong terminolgies here !

Shawn..

With your permission, we can take this one step at a time... let's first try to enumerate all the user's templates (addins?) to see if we can get a handle to them. Try running this script to see if the template(s) in question show up...

code:

---

break on cls
$word = olecreateobject("word.application")
if $word
 $addins = val("&"+olegetproperty($word,"addins"))
 if $addins
  $enum = oleenumobject($addins)
  if $enum
   $addin = oleenumobject($addins,$enum)
   if $addin
    ?"Addins:"
    while @error = 0
     ? olegetproperty($addin,"name")
     $= olereleaseobject($addin)
     $addin = oleenumobject($addins,$enum)
    loop
    $= olereleaseobject($addin)
   endif
 
   $= olereleaseobject($enum)
  endif
  $= olereleaseobject($addins)
 endif
 $= olecallfunc($word,"quit")
 $= olereleaseobject($word)
endif
exit

---

Shawn.

[This message has been edited by Shawn (edited 29 March 2001).]

you still with us ?

kirm

while @error = 0
? olegetproperty($addin,"name")
$= olereleaseobject($addin)
$addin = oleenumobject($addins,$enum)
loop

It goes through the loop once and continues on. I wanted to see what was happening so I added this

$r=olegetproperty($addin,"name")
? "addin is " + $r

I think this is what the second line of the loop is supposed to do but I wanted confimation.

Anyhow this is what I get:

addin is

Obviously olegetproperty($addin,"name") isn't returning anything. What does this mean? I assume this isn't a good sign. I am also assuming(I know little about OLE) that you were trying to enumerate the add-ins in word, Shawn. Is that correct? I can tell you that I do have the macro installed and I don't know why it isn't being returned unless addins doesn't include macros. That doesn't make sense though.

Anyhow that was a cool exercise. Thanks Shawn. If you have any other ideas let me know.

Kirm

P.S. How's the weather in TO? Here it sucks. I've had the opportunity to visit your city once about 6 years ago and I was very impressed. It's a beautiful city.

Didn't see that your from Edmonton. Weather is mild here today... how's things out West ?

Anyway, from one hoser to another...

try changing this line...

$addins = val("&"+olegetproperty($word,"addins"))

to this...

$addins = val("&"+olegetproperty($word,"templates"))

Any different ?

Shawn.

[This message has been edited by Shawn (edited 02 April 2001).]

This has become a bit of a vandetta on my part... you've probably got some work-around by now and if you do - cudo's. But now it's just gotten personal. We Canadians can be persistent bastards, can't we ?

This script will do two things...

1) Enumerate all the VB CodeModules (macros) in Normal.dot

2) Add a VB macro module into normal.dot if it doesn't already exist.

One can manually see and verify all the module names and sourcecode using the following winword menu item ...

tools->macro->macros...->organizer

Always use the organizer when managing macro modules (adding,deleting).

Here's the macro module. Change the script variable $module_file to point to the module.

[file: kixtart.bas]

code:

---

Attribute VB_Name = "KiXtart"
Sub KixRox()
Attribute KIXTART.VB_Description = "Macro recorded 10/08/99 by Shawn"
Attribute KIXTART.VB_ProcData.VB_Invoke_Func = "Normal.KiXtart.KixRox"

'
' KIXTART Macro
' Macro recorded 10/08/99 by Shawn
'
	Selection.TypeText Text:="KiXtart 2001 Rox !"

End Sub

---

and the script...

code:

---

break on cls

$module_name = "kixtart"              ; <--- module name ?
$module_file = "m:\macro\kixtart.bas" ; <--- and the filename ?

$vb_ext_ct_classmodule = "1"

$word = olecreateobject("word.application")

if $word

 $template = val("&"+olegetproperty($word,"NormalTemplate"))

 if $template

  $document = val("&"+olecallfunc($template,"openasdocument"))

  if $document

   $vbproject = val("&"+olegetproperty($document,"vbproject"))

   if $vbproject

    $vbcomponents = val("&"+olegetproperty($vbproject,"vbcomponents"))

    if $vbcomponents
     $index = 1
     $component = val("&"+olecallfunc($vbcomponents,"item","i","$index"))

     while @error = 0

      $name = olegetproperty($component,"name")
      $type = olegetproperty($component,"type")

      if $name = "$module_name" and $type = "$vb_ext_ct_classmodule"
       $classmodule = $component
      else
       $= olereleaseobject($component)
      endif
      $index = $index + 1
      $component = val("&"+olecallfunc($vbcomponents,"item","i","$index"))
     loop

     $= olereleaseobject($component)

     if $classmodule
      ?"$module_name module already loaded!"
      $= olereleaseobject($classmodule)
     else
      ?"Loading $module_name module ... "
      $new= val("&"+olecallfunc($vbcomponents,"import","s","$module_file")) "@serror"
      $= olereleaseobject($new)
     endif

     $= olereleaseobject($vbcomponents)

    endif

    $= olereleaseobject($vbproject)

   endif
   $= olereleaseobject($document)

  endif
  $= olereleaseobject($template)
 endif

; ?"pause..." gets $k

 $= olecallfunc($word,"quit")

 $= olereleaseobject($word)

endif

exit

---

Shawn.

[This message has been edited by Shawn (edited 04 April 2001).]

Kirm

Kirm

Also where did you learn about that undocumented "s" typelist?(typelist is what the help file calls it).

You used it here:

olecallfunc($vbcomponents,"import","s","$module_file")

Anyway, I still can't believe it works! There really isn't anything that Kixtart can't do.

Kirm

Kirm

No need for apology, your testing the crap out of it and that's a good thing ! One more test for you though. Make sure that when the script finishes, winword.exe terminates cleanly and is NOT still running in the background. I was extra careful to perform proper object cleanup in this script. Winword should exit cleanly. Have a double check though...

The "s" typelist thingy is just something, someone tried along time ago and got to work. Still hasn't made it's way into the documentation yet, eh (?)

Good sources of information ? I just basically hunt and peck around MSDN ! If your interested in learning more about OLE and Automation, here's a link for you...

Microsoft Word Objects

Been a pleasure.

Shawn.