I have logged a call with worksite support regarding this but thought someone here might be able to help in the meantime.We are testing the integration of our current custom vba templates with the Interwoven 8.2 Desksite/Filesite client, which we have yet to deploy.
We have noticed an issue where the creation of an instance of an iManO2K.iManageExtensibility object is affected by the DelayedLogin option.
In our code, we have a public property as follows:
Public Property Get IManageExt() As iManO2K.iManageExtensibility
If m_IManExtObj Is Nothing Then
Set m_IManExtObj = m_WordApp.COMAddIns("iManO2K.AddinForWord2000").Object
End If
Set IManageExt = m_IManExtObj
End Property
As part of the procedure that is called when a new document is created, the above property is referenced in the code:
IManageExt.Context("NRTDMS")
If the DelayedLogin option is on and we attempt to create a new document after opening Word, and no other document has been opened directly from Filesite, then we get a "Run-time error 5 -- Invalid procedure call or argument".
If we examine the ImanageExt property from within the code, the above error is not surprising as the Context collection has no items in it.
However, if we turn the DelayedLogin option off and examine the same property at the same point in the code, the Context property contains the expected "NRTDMS" context item and our code runs through with no errors.
So it appears that the DelayedLogin option is affecting the behaviour of the iManO2K.iManageExtensibility class constructer.
We want to use the DelayedLogin feature and therefore need to know how we can create an instance of the iManO2K.iManageExtensibility object so that it contains the "NRTDMS" context items as it does when the DelayedLogin is off (or as it behaved with v8.0 of the filesite client).
Technical Environment Summary:
-Word 2002
-Windows XP
-Desksite/Filesite 8.2
