Outlook Add-In

[tward]

OK, I have the Outlook Add-In, it works on the Development machine,
but how do you deploy it now?

It makes a .DLL and I've tried installing that on another machine and registering it and when it starts I get a "Can't Create ActiveX control"....

Can't figure out what I am missing on the Deployment machine!

I looked at [FAQ's: OD] How do I use VB 6 to make an Add-In for an Office application? but it doesn't really say anything about deployment...

[MartinLiss]

Moved.

[randem]

You are missing all the dependencies that your program needs....

[tward]

You are missing all the dependencies that your program needs....

I of course tried PDW without success...

Also tried manually trying to figure out what exactly I needed but still no go....

My deployment machine has the VBRuntime stuff on it... Dependency check doesn't show anything different than what I already have...

[randem]

Check your PM

[RobDog888]

You shouldnt need to create a package for an AddIn unless you are using additional resources like ADO or a form with a ocx control etc. What does your AddIn do?

[tward]

You shouldnt need to create a package for an AddIn unless you are using additional resources like ADO or a form with a ocx control etc. What does your AddIn do?

That is what I thought as well. It is not real complicated. It simply checks to make sure that the Subject Line is not blank before sending the message. If it is blank it displays a messagebox and cancels the send.

[RobDog888]

Then perhaps its a Outlook version issue. Is the target system running the same version of Outlook?

[tward]

Then perhaps its a Outlook version issue. Is the target system running the same version of Outlook?

Deployment machine has 11.8010.8107 SP2
Development machine has 11.6568.6568 SP2

Guess I have to try and track down exactly where the

"Run-time error '429':

ActiveX component can't create object

is comming from......

[tward]

Can't figure out exactly what I am doing wrong.

Something stupid, I'm guessing...

[tward]

One more bit of information, the Add-In causes an Error the first time it is used, as long as I trap the error, it will work the second time....

Funny that it works fine on the development machine, that is why I thought it was a deployment problem, may be more of a problem with the add-in code itself..

[RobDog888]

Well if its working the second time then its not missing any references then. I'll look through your code.

[RobDog888]

Sure he did. Post #1 and #9.

[randem]

Then that would be you attempt to use the control before you create it and by the second time you actually create it. Are you creating controls dynamically?

[RobDog888]

Right, but i dont see anything yet that looks like that would be the case.

[RobDog888]

Worked perfect the very first time for me. 11.8010.8107 SP2

[randem]

Ok, So how does one use this Add-In to test it?

[randem]

Works perfectly for me also...

[RobDog888]

To debug/test an AddIn you need to open the project, add a breakpoint on the OnConnection sub, then in the project properties choose "Start program" under the debugging tab, and select the path to your outlook.exe, then Run with full compile. Make sure Outlook is not running first as VB 6 will start it for you. Then you can step through the procedures and test it by creating a test email with no subject.

[RobDog888]

@tward... is the error message from the oApp_ItemSend procedure or somewhere else?

[tward]

From oApp_ItemSend...

[RobDog888]

So then that means that the event if firing and thusly the oApp application object is being initialized from the OnConnection sub correctly. If it wasnt then the event wouldnt first with your oApp_ItemSend in the msgbox title but would be a generic vb error msg.

this is being tested for sending of an email and anot a meeting request or other object? Is word selected as the default email client editor for mail messages?

[tward]

Yes, I am testing it when sending an email and Word is the default editor on both machines.

I have actually just tracked it down to the following line that is causing the problem:

frmMessageBox.Show vbModal

Odd... Why would it fail on a form?

I do notice that the first time I press "New" message on the machine with the problem, I get the following error:

"Runtime Error '-214746259 (80004005)'
Method '~' of object '~' failed"

[tward]

It will work fine if I use a messagebox instead of my own custom form. The problem is that the messagebox appears behind the email message so it appears to lock outlook up unless you switch to Outlook... Another words the messagebox comes up in front of Outlook instead of the Message....

[tward]

This actually fixes it (just hiding the error on the Loading of the form), then showing the form and it seems to work..

Don't really know why I get that error on trying to load a form..

[RobDog888]

There are other ways to set the form as TopMost so it doesnt interfere with Outlook, but we both tested it out and we didnt get that error. Could it be a bug in that version of Outlook? It doesnt appear to be patched with the latest updates.

[tward]

I would have liked to use just a standard msgbox command, but that is the one that comes up behind the mail window...

A bug with my development Outlook?

The deployment machine is the same version that you said it worked on for you....

The error had to do with simply loading the form though....

I can't explain what is going on, but ignoring the error (which I don't usually like to do) when I do the Load frmMessageBox, causes the frmMessageBox.Show vbModal to work fine!

[RobDog888]

What about loading the form but not showing it until you need to display it?

Load Form1

[tward]

That is what the new version I attached is doing....

The load causes the error I was getting, but I just ignore it and then Show in Modally which seems to work just fine...

[RobDog888]

Oh well at least its working for you now. Just wondering why it doesnt work under your target system yet works on ours.

[tward]

Wish I knew.....