Problems with IManO2K.dot and Office 2007

Hello.

I've been trying to port some VBA code from Word 2003 to Word 2007. (Specifically from Office 2003 with Worksite 8.0(SP1) running inside WindowsXP to Office 2007 with Worksite 8.2(SP1) running inside Windows Vista. Our long term plan is to do away with as much VBA code as possible, but as part of the transition we still have to get some legacy code working on the new desktop.

Unfortunately though, I'm having trouble getting the NRTDMS object from within Word VBA code. I think it's using the iManO2K.dot Word template that's distributed with Worksite. I inherited the code from someone who left long ago, and unfortunately I'm having some trouble finding documentation on IManO2K.dot, so I'm not entirely sure where to look for information about how it should be done. If anyone can offer some insight or point me in the right direction, I'd really appreciate it.

Below, I've included a code extract which acts differently in Word 2007 from how it acted in Word 2003. The specific problem seems to be that in 2007, the NRTDMS object isn't being included as part of the IMANEXTLib.ContextItems object that's returned from the iManO2K addin.

Does anyone know if something's changed between integration for the two versions? Should the code be using some completely different method of integrating with Office 2007?

Thanks for any help.
Mike.

====


'Return the current nrtdms object.
Function GetNRTDMS() As IManage.NRTDMS
    Set GetNRTDMS = Nothing

    Dim objComAddin As Office.COMAddIn
    Dim objO2KExt As iManO2K.iManageExtensibility
    Dim pContextItems As IMANEXTLib.ContextItems

    'Get the iManO2K add-in from the add-ins collection.
    Set objComAddin = Application.COMAddIns("iManO2K.AddinForWord2000")

    If Not objComAddin.Connect Then
        MsgBox "The iManage add-in isn't enabled", vbOKOnly, "Error in GetNRTDMS()"
        Exit Function
    End If

    'The objComAddin Object property is the extensibility object.
    Set objO2KExt = objComAddin.Object
    Set pContextItems = objO2KExt.Context

    If pContextItems.Count = 0 Then
        'This branch is entered under Word 2007, but not under Word 2003.
        MsgBox "pContextItems.count should not be 0!", vbOKOnly, "Error in GetNRTDMS()"
        Exit Function
    End If

    Set GetNRTDMS = pContextItems.Item("NRTDMS")

End Function 'GetNRTDMS

Find more posts tagged with

Comments

guido1

Isn't the COM integration with Office 2007 only supported for client version 8.2 SP1?

Also I think this may be only supported for the Windows Vista OS, but I may've got my wires crossed there.

izogi

Hi Guido.

Isn't the COM integration with Office 2007 only supported for client version 8.2 SP1?

Also I think this may be only supported for the Windows Vista OS, but I may've got my wires crossed there.

I believe this is correct, although 8.2(SP1) on Vista is exactly what I have installed on the test platform, and I've been unable to get it to work. (Sorry if I didn't word this well earlier.) Initially I thought it might be because we were running the Release Candidate of SP1. I've since upgraded it to the official SP1 release, but am still seeing the same behaviour.

I was wondering if there was supposed to be an IManO2007.dot or something that I should be using instead of IManO2K.dot.

Thanks for the response in any case.
Mike.

guido1

The "iManO2k.dot" VBA add-in isn't in itself responsible for the integration with Microsoft Word application. It's there solely to provide integration with shortcut key assignments (KeyBindings) in Word, which can only be assigned to macros. This is a limitation of the Word object model.

The actual COM integration add-in is a compiled library located in the main WorkSite folder. For example, for Office XP & Office 2003 the file responsible is iManOXP.dll

Having said all that.. sorry I can't help with your specific issue!

izogi

Thanks for the info, it might give me a starting point. (For one thing, I'll go and investigate that assembly more closely.) I'll post something back here if I figure out what's wrong.

izogi

Well I still haven't figured out what's causing the original problem, but I may have a workaround which could at least get the job done, however ugly.

I'm experimenting with rewriting the GetNRTDMS() function so it gets the NRTDMS object from the active document, which is obtained through its working path. Anecdotally it seems to be working for at least some things, although there are a few assumptions about having a current document open which is a Worksite document, and probably a heap of other things that I haven't thought of yet.

Here it is:


' Returns the iManage Document object associated with the ActiveWindow
Public Function GetActiveDocument() As NRTDocument
    Dim objComAddin As Office.COMAddIn
    Dim objExtensibility As iManO2K.iManageExtensibility

    On Error GoTo errHandler

    If Documents.Count = 0 Then             'no documents are open
        Exit Function
    End If

    'get the iManO2K add-in from the add-ins collection
    Set objComAddin = Application.COMAddIns("iManO2K.AddinForWord2000")

    If objComAddin.Connect = False Then     'the iManage add-in isn't enabled
        Exit Function
    End If

    'the objComAddin Object property is the extensibility object
    Set objExtensibility = objComAddin.Object

    If (objExtensibility.CurrentMode = nrConnectedMode) Or (objExtensibility.CurrentMode = nrPortableMode) Then
        Set GetActiveDocument = objExtensibility.GetDocumentFromPath(ActiveDocument.FullName)
    End If

    Set objExtensibility = Nothing
    Set objComAddin = Nothing

    Exit Function

errHandler:

    MsgBox Err.Number & vbLf & Err.Description, vbCritical + vbOKOnly, "Create Worksite Document Object"
    Err.Clear

    Set objExtensibility = Nothing
    Set objComAddin = Nothing
End Function


Function GetNRTDMS() As IManage.NRTDMS
    Dim currentDoc As IManage.NRTDocument
    Set currentDoc = iManInform.GetActiveDocument
    Set GetNRTDMS = currentDoc.Database.Session.NRTDMS
    Set currentDoc = Nothing
End Function

jny

The iManO2k.dot is, indeed, a template that is merely used to hijack keyboard buttons as part of the WorkSite Office Integration.

In a nutshell...

The Office Integration is a compiled source to a Word Add-In. This Add-In has a CLSID that is registered in the registry.

The Add-In for Office 2007 is the same as the previous version except it's wrapped around .NET code; this shim is now responsible for loading the

Add-In, and it has a different name which is oUTR02K.Connect.

In your code, you would now get a handle to the extensibility object through this new name versus the former one, iManO2K.AddinForWord2000, like so:

Dim objIManageExtensibility As iManO2K.iManageExtensibility
Set objIManageExtensibility = Application.COMAddIns("oUTR02K.Connect").Object

The consumption of the methods and properties of the extensibility object should be the same, including the use of the iManO2K.iManageExtensibility.Context("NRTDMS") Method.

izogi

In your code, you would now get a handle to the extensibility object through this new name versus the former one, iManO2K.AddinForWord2000, like so:

[----snip----]

Brilliant -- this change seems to have fixed the problem. Thanks for the help.

Mike.