openCMD - checks out doc but doesn't launch

This must be something obvious that I'm missing!

Trying to use the iManExtLib OpenCmd object to open a document - everything's fine apart from the fact it doesn't actually launch! The document is checked out, and exists in the NRPORTBL checkout path, and can subsequently be checked back in, but just doesn't launch. No error is thrown either. I think I've been looking at it too long!

Here's the vb.net code (targetDoc is an iManDocument):

Dim pOpenCmd As IMANEXTLib.OpenCmd
Dim pContextItems As IMANEXTLib.ContextItems
Dim pDocArray(0) As IManage.NRTDocument
Dim hWnd As Long
pContextItems = New IMANEXTLib.ContextItems
pOpenCmd = New IMANEXTLib.OpenCmd
pDocArray(0) = targetDoc
pContextItems.Add("ParentWindow", hWnd)
pContextItems.Add("SelectedNRTDocuments", pDocArray)
pContextItems.Add("IManExt.OpenCmd.NoCmdUI", Nothing)
pContextItems.Add("IManExt.OpenCmd.Integration", True)
pOpenCmd.Initialize(pContextItems)
pOpenCmd.Update()
pOpenCmd.Execute()
Response.Write(pContextItems.Item("IManExt.OpenCmd.ING.FileLocation"))

Everything looks fine, and the file location returned is right. This is all being run on the webserver (an XP workstation with Filesite 8.2 and Office).

Can anyone point out the (hopefully obvious) error? Only thing I can think is its to do with hWnd, not sure how I should be setting, getting or handling that.

thanks!

Find more posts tagged with

Comments

guido1

I don't think the window handle is mandatory for this command, so you can leave out the "ParentWindow" context item

More likely your problem is that you're setting the "IManExt.OpenCmd.NoCmdUI" context item to Nothing, when I believe it should be a boolean data type.

Set it to True if you don't want to display any UI as a result of opening the document.

izogi

Hi Jason.

Trying to use the iManExtLib OpenCmd object to open a document - everything's fine apart from the fact it doesn't actually launch! The document is checked out, and exists in the NRPORTBL checkout path, and can subsequently be checked back in, but just doesn't launch. No error is thrown either. I think I've been looking at it too long!

This probably won't answer your question and I don't know if it's exactly the same issue, but I remember having some problems with the IMANEXTLib.OpenCmd command object about six months ago.

I narrowed it down to cases where I was trying to open documents that were Outlook emails, and having Desksite open in the background at the same time. I'd thought that being compiled for the DotNet 2 CLR also had something to do with it (as opposed to DotNet 1.1), but I think I ruled that out in the end.

I created a thread in this forum, which is visible at http://devnet.interwoven.com/forums_vb/showthread.php?t=21878&forumid=49 , but unfortunately there weren't any responses. I attached some sample C# code to that post though which demonstrated my problem, so you could possibly try it out and see if it works any better for you.

I didn't noticed whether the document was being checked out or not, but it wasn't opening. I've since re-written the code with a workaround hack so that it connects to the server to get as much meta info about the document as possible, then writes a .NRL file to a temporary location, and calls System.Diagnostics.Process.Start(filename) to open it. (Yuck). I guess this might or might not be an option for you depending on how complex your setup is.

izogi

Hi again.

I forgot to mention that the example that I attached to my thread from August was actually a Windows Forms program, and it's getting its window handle from a very temporary window which was designed to never actually be visible (the .Visible property is always supposed to be false), and it lasts only for the duration of opening a document. This seemed to work in general, except for the problem I was pointing out about not being able to open Outlook email documents for some reason.

The Worksite Extension Library Reference Manual seems to say that the ParentWindow field is mandatory for OpenCmd, at least for Worksite 8.0, but Guido might be right and it could possibly still work without that.

Mike.