May I suggest you try to troubleshoot this using either Debug.trace() or force a launch of the debug pane and use the "watch" feature there. ('Watch' is a Tab in debug pane... Right Click and then set it to monitor several of your Publication and Page variables. The purpose is to see what is happening with your actions.
for the
Quote:
*var*.DestroyClonedObject
you want to confirm that that variable actually contains the ILM Object, and not just a textual name.
Use the Debug.trace command. This has always been a tricky area for me. In some cases you can get to the Object directly. At other times (when I think I have the Object), I have just the name. In that case, you may have to construct a concatenating expression and then use eval() command. [continue here/link, or Search Forum:
viewtopic.php?t=2102&highlight=clone+name ]
Rather than detail that here, please search the Forum for 'clone' AND 'name' (w/o quotes etc). There you will find not only explanation but downloadable examples... there are many variations in how to approach this
(depending on your 'up-front' strategy in creating and naming the Clones).
I'd offer 'more', but I have limited experience in this area. Something I want to build upon, but not yet there.
Bottomline: the
xxvarxx before the .DestroyClonedObject()
needs to be an Object. Otherwise, the eval() command is often used to force this recognition. At other times, the keyword 'this' can be used to pick up the object itself and your variable may be able to carry it over
as an object. (Whew! isn't that confusing? If I have not said it correctly, at least it may serve as a 'heads up' what to look for). Another way to think on it: if you have myVar02 = VectorDOT.CloneObject(x,y,vis) ... you are referencing the Object itself. If however you have set myVar02 = SomeObjectName ... you are only storing a text string/name. So this is another hint to 'capture' the Object_Clone
at time of cloning and possibly even write that to the DB (??) (you will see examples of people here
using Arrays to store "object").
Cheers,
Larry
ps. I viewed your Pub, but did not get too far. Mostly the DB path was not vaild for me and I did not want to hassle with managing an ODBC connection set-up etc etc. But from what I viewed, I think the above should help.