add-in won't load

Status
Not open for further replies.
J

Jason

One of out customer installed multiple add-ins.

Our older version worked on his machine but not the newer version.

Disable or remove all other add-ins from Outlook add-in manager, re-enable

or reinstall our add-in won't work.

Reinstall Outlook won't work.

Add VSTO environmental variable does not help, not showing or logging

anything.

The loadstatus of registry key is the OK value 3 before uninstall and after

reinstall our add-in.

Other machines have no problem.

Any thoughts?
 
K

Ken Slovak - [MVP - Outlook]

No way for us to know what's going on. You need to use managed code

debugging and Fusion logging to see what's going on, assuming that your

addin is failing to load. If it is loading then you need to run in debug

mode and add lots of error logging to see where things fail.

Assuming the addin just fails to load at all, see

http://blogs.msdn.com/vsod/archive/2008/04/22/Troubleshooting-com-add-in-load-failures.aspx

for information on troubleshooting addin load failures with managed code.

"Jason" <a@a.com> wrote in message

news:OWY%23%23$IsJHA.4564@TK2MSFTNGP02.phx.gbl...
> One of out customer installed multiple add-ins.
> Our older version worked on his machine but not the newer version.
> Disable or remove all other add-ins from Outlook add-in manager, re-enable
> or reinstall our add-in won't work.
> Reinstall Outlook won't work.
> Add VSTO environmental variable does not help, not showing or logging
> anything.
> The loadstatus of registry key is the OK value 3 before uninstall and
> after reinstall our add-in.
> Other machines have no problem.

> Any thoughts?

>
 
J

Jason

The add-in did not load at all. There is logging as the very 1st statemnt in

startup event handler. Nothing logged.

We'll try the new tips. Thanks Ken.
<kenslovak@mvps.org> wrote in message

news:uaY2RkUsJHA.4324@TK2MSFTNGP05.phx.gbl...
> No way for us to know what's going on. You need to use managed code
> debugging and Fusion logging to see what's going on, assuming that your
> addin is failing to load. If it is loading then you need to run in debug
> mode and add lots of error logging to see where things fail.

> Assuming the addin just fails to load at all, see
> http://blogs.msdn.com/vsod/archive/2008/04/22/Troubleshooting-com-add-in-load-failures.aspx
> for information on troubleshooting addin load failures with managed code.

> >

>

> "Jason" <a@a.com> wrote in message
> news:OWY%23%23$IsJHA.4564@TK2MSFTNGP02.phx.gbl...
> > One of out customer installed multiple add-ins.
> > Our older version worked on his machine but not the newer version.
> > Disable or remove all other add-ins from Outlook add-in manager,
> > re-enable or reinstall our add-in won't work.
> > Reinstall Outlook won't work.
> > Add VSTO environmental variable does not help, not showing or logging
> > anything.
> > The loadstatus of registry key is the OK value 3 before uninstall and
> > after reinstall our add-in.
> > Other machines have no problem.
>

>> Any thoughts?
>

>>

>
 
J

Jason

The add-in was in the Disabled Items list. After enable it, the add-in was

loaded and the menu appeared. But now email won't go out. They stay in

Outbox forever.

I remember someone had the same email problem and asked for help a while ago

but I could not retrive the mail.It was gone.

"Jason" <a@a.com> wrote in message

news:OjSL5SasJHA.3848@TK2MSFTNGP02.phx.gbl...
> The add-in did not load at all. There is logging as the very 1st statemnt
> in startup event handler. Nothing logged.

> We'll try the new tips. Thanks Ken.

> " - " <kenslovak@mvps.org> wrote in message
> news:uaY2RkUsJHA.4324@TK2MSFTNGP05.phx.gbl...
> > No way for us to know what's going on. You need to use managed code
> > debugging and Fusion logging to see what's going on, assuming that your
> > addin is failing to load. If it is loading then you need to run in debug
> > mode and add lots of error logging to see where things fail.
>

>> Assuming the addin just fails to load at all, see
> > http://blogs.msdn.com/vsod/archive/2008/04/22/Troubleshooting-com-add-in-load-failures.aspx
> > for information on troubleshooting addin load failures with managed code.
>

>> > >

> >

>

>
>
>
>
>
>> "Jason" <a@a.com> wrote in message
> > news:OWY%23%23$IsJHA.4564@TK2MSFTNGP02.phx.gbl...
> >> One of out customer installed multiple add-ins.
> >> Our older version worked on his machine but not the newer version.
> >> Disable or remove all other add-ins from Outlook add-in manager,
> >> re-enable or reinstall our add-in won't work.
> >> Reinstall Outlook won't work.
> >> Add VSTO environmental variable does not help, not showing or logging
> >> anything.
> >> The loadstatus of registry key is the OK value 3 before uninstall and
> >> after reinstall our add-in.
> >> Other machines have no problem.
> >
>>> Any thoughts?
> >
>>>

> >


>
 
K

Ken Slovak - [MVP - Outlook]

Usually if an addin is disabled that way it means you have unhandled

exceptions, a cardinal sin for addins. Or that you aren't using a shim to

get your own AppDomain for the addin and some other code in that same

AppDomain is crashing Outlook or has unhandled exceptions.

If it remains in Outbox are you messing with the items after they're sent,

or accessing them in Outbox, or not releasing the object references?

"Jason" <a@a.com> wrote in message

news:O4gL1FisJHA.2776@TK2MSFTNGP03.phx.gbl...
> The add-in was in the Disabled Items list. After enable it, the add-in was
> loaded and the menu appeared. But now email won't go out. They stay in
> Outbox forever.

> I remember someone had the same email problem and asked for help a while
> ago but I could not retrive the mail.It was gone.
 
J

Jason

The problem of mail not going out only occurs on Outlook 2007, not 2003.

I believe it is caused by the interception of Explorer's SelectionChange

event.

//class level variable to hold event handler

private Outlook.Explorer explorer = null;

private void ThisAddIn_Startup(object sender, System.EventArgs e)

{

explorer = this.Application.ActiveExplorer();

explorer.SelectionChange += new

Outlook.ExplorerEvents_10_SelectionChangeEventHandler(ThisAddIn_SelectionChanged);

}

private void ThisAddIn_SelectionChanged()

{

// only handle appointments, nothing else

if (explorer.Selection.Count > 0 && explorer.Selection[1] is

Outlook.AppointmentItem)

{

> ..

}

}

Once a new mail is created, Outlook put it into Outbox folder and fires 3

SelectionChange events.

I know JavaScript DOM event bubble up and vaguely remember one article

mentioned about passing Outlook event out of event handler. How do I pass

the Explorer's SelectionChange event back to Outlook, so Outlook can handle

it as usual?
<kenslovak@mvps.org> wrote in message

news:Oq84NlisJHA.1088@TK2MSFTNGP04.phx.gbl...
> Usually if an addin is disabled that way it means you have unhandled
> exceptions, a cardinal sin for addins. Or that you aren't using a shim to
> get your own AppDomain for the addin and some other code in that same
> AppDomain is crashing Outlook or has unhandled exceptions.

> If it remains in Outbox are you messing with the items after they're sent,
> or accessing them in Outbox, or not releasing the object references?

> >

>

> "Jason" <a@a.com> wrote in message
> news:O4gL1FisJHA.2776@TK2MSFTNGP03.phx.gbl...
> > The add-in was in the Disabled Items list. After enable it, the add-in
> > was loaded and the menu appeared. But now email won't go out. They stay
> > in Outbox forever.
>

>> I remember someone had the same email problem and asked for help a while
> > ago but I could not retrive the mail.It was gone.

>
 
K

Ken Slovak - [MVP - Outlook]

You don't need to do anything for passing the event back to Outlook, it's

Outlook that fires the event for you. It will also only fire the event on an

Explorer you have instantiated, so this event should not be firing in Outbox

unless you switch the Explorer to viewing the Outbox. You should not be

doing that if that's what you are doing. Leave things in Outbox alone and

don't mess with them after sending or the items will just remain in Outbox

and never get sent.

"Jason" <a@a.com> wrote in message

news:%23xwXrXstJHA.2776@TK2MSFTNGP03.phx.gbl...
> The problem of mail not going out only occurs on Outlook 2007, not 2003.

> I believe it is caused by the interception of Explorer's SelectionChange
> event.

> //class level variable to hold event handler
> private Outlook.Explorer explorer = null;

> private void ThisAddIn_Startup(object sender, System.EventArgs e)
> {
> explorer = this.Application.ActiveExplorer();
> explorer.SelectionChange += new
> Outlook.ExplorerEvents_10_SelectionChangeEventHandler(ThisAddIn_SelectionChanged);
> }

> private void ThisAddIn_SelectionChanged()
> {
> // only handle appointments, nothing else
> if (explorer.Selection.Count > 0 && explorer.Selection[1] is
> Outlook.AppointmentItem)
> {
> ...
> }
> }

> Once a new mail is created, Outlook put it into Outbox folder and fires 3
> SelectionChange events.

> I know JavaScript DOM event bubble up and vaguely remember one article
> mentioned about passing Outlook event out of event handler. How do I pass
> the Explorer's SelectionChange event back to Outlook, so Outlook can
> handle it as usual?
 
J

Jason

Yes you are right. The problem only occurs when user clicks the Outbox

folder then create a new mail. No problem if user has not highlighted the

Outbox.

Once the mail is stalled, no matter how many times you click Send and

Receive button, it will stay there forever, even after user move to other

folder or restart Outlook. You have to delete it, and create an new mail.

What can I do then? Tell user not to select Outbox, or unselect the Outbox

programmatically if user does that?
<kenslovak@mvps.org> wrote in message

news:%23f$JhjstJHA.4592@TK2MSFTNGP06.phx.gbl...
> You don't need to do anything for passing the event back to Outlook, it's
> Outlook that fires the event for you. It will also only fire the event on
> an Explorer you have instantiated, so this event should not be firing in
> Outbox unless you switch the Explorer to viewing the Outbox. You should
> not be doing that if that's what you are doing. Leave things in Outbox
> alone and don't mess with them after sending or the items will just remain
> in Outbox and never get sent.

> >

>

> "Jason" <a@a.com> wrote in message
> news:%23xwXrXstJHA.2776@TK2MSFTNGP03.phx.gbl...
> > The problem of mail not going out only occurs on Outlook 2007, not 2003.
>

>> I believe it is caused by the interception of Explorer's SelectionChange
> > event.
>

>> //class level variable to hold event handler
> > private Outlook.Explorer explorer = null;
>

>> private void ThisAddIn_Startup(object sender, System.EventArgs e)
> > {
> > explorer = this.Application.ActiveExplorer();
> > explorer.SelectionChange += new
> > Outlook.ExplorerEvents_10_SelectionChangeEventHandler(ThisAddIn_SelectionChanged);
> > }
>

>> private void ThisAddIn_SelectionChanged()
> > {
> > // only handle appointments, nothing else
> > if (explorer.Selection.Count > 0 && explorer.Selection[1] is
> > Outlook.AppointmentItem)
> > {
> > ...
> > }
> > }
>

>> Once a new mail is created, Outlook put it into Outbox folder and fires 3
> > SelectionChange events.
>

>> I know JavaScript DOM event bubble up and vaguely remember one article
> > mentioned about passing Outlook event out of event handler. How do I pass
> > the Explorer's SelectionChange event back to Outlook, so Outlook can
> > handle it as usual?

>
 
J

Jason

Now the problem of email won't go out also occurs on Outlook 2003. So it is

not 2007 specific.

After comment out the explorer.SelectionChange, emailing resumes normal.

explorer.SelectionChange +=

new

Outlook.ExplorerEvents_10_SelectionChangeEventHandle(ThisAddIn_SelectionChanged);

The reason of using explorer.SelectionChange is to catch EntryIDs of the

appointments to be deleted.

The Email problem has been fixed in Outlook 2007 by replacing

SelectionChange with BeforeItemMove event.

What is the feasible solution for 2003?

I'll start a new thread.

"Jason" <a@a.com> wrote in message

news:%23zkIOkttJHA.4592@TK2MSFTNGP06.phx.gbl...
> Yes you are right. The problem only occurs when user clicks the Outbox
> folder then create a new mail. No problem if user has not highlighted the
> Outbox.

> Once the mail is stalled, no matter how many times you click Send and
> Receive button, it will stay there forever, even after user move to other
> folder or restart Outlook. You have to delete it, and create an new mail.

> What can I do then? Tell user not to select Outbox, or unselect the Outbox
> programmatically if user does that?

> " - " <kenslovak@mvps.org> wrote in message
> news:%23f$JhjstJHA.4592@TK2MSFTNGP06.phx.gbl...
> > You don't need to do anything for passing the event back to Outlook, it's
> > Outlook that fires the event for you. It will also only fire the event on
> > an Explorer you have instantiated, so this event should not be firing in
> > Outbox unless you switch the Explorer to viewing the Outbox. You should
> > not be doing that if that's what you are doing. Leave things in Outbox
> > alone and don't mess with them after sending or the items will just
> > remain in Outbox and never get sent.
>

>> > >

> >

>

>
>
>
>
>
>> "Jason" <a@a.com> wrote in message
> > news:%23xwXrXstJHA.2776@TK2MSFTNGP03.phx.gbl...
> >> The problem of mail not going out only occurs on Outlook 2007, not 2003.
> >
>>> I believe it is caused by the interception of Explorer's SelectionChange
> >> event.
> >
>>> //class level variable to hold event handler
> >> private Outlook.Explorer explorer = null;
> >
>>> private void ThisAddIn_Startup(object sender, System.EventArgs e)
> >> {
> >> explorer = this.Application.ActiveExplorer();
> >> explorer.SelectionChange += new
> >> Outlook.ExplorerEvents_10_SelectionChangeEventHandler(ThisAddIn_SelectionChanged);
> >> }
> >
>>> private void ThisAddIn_SelectionChanged()
> >> {
> >> // only handle appointments, nothing else
> >> if (explorer.Selection.Count > 0 && explorer.Selection[1] is
> >> Outlook.AppointmentItem)
> >> {
> >> ...
> >> }
> >> }
> >
>>> Once a new mail is created, Outlook put it into Outbox folder and fires
> >> 3 SelectionChange events.
> >
>>> I know JavaScript DOM event bubble up and vaguely remember one article
> >> mentioned about passing Outlook event out of event handler. How do I
> >> pass the Explorer's SelectionChange event back to Outlook, so Outlook
> >> can handle it as usual?

> >


>
 
K

Ken Slovak - [MVP - Outlook]

Please do not start new threads for the same problem. It just confuses

things.

If items in the Outbox are messed with using code then they won't go out.

That is true of all Outlook versions. So the simple answer is don't do that.

There's no need to do it, so don't.

If the ActiveExplorer.CurrentFolder is Outbox just don't handle

SelectionChange() there. If it's not Outbox you can safely handle

SelectionChange(). Since BeforeFolderSwitch() will fire before the folder in

the Explorer is switched to Outbox you will know when that happens. So just

remove the SelectionChange() handler then and reinstate it when the folder

isn't Outbox.

"Jason" <a@a.com> wrote in message

news:OGKSLy4tJHA.496@TK2MSFTNGP06.phx.gbl...
> Now the problem of email won't go out also occurs on Outlook 2003. So it
> is not 2007 specific.

> After comment out the explorer.SelectionChange, emailing resumes normal.

> explorer.SelectionChange +=
> new
> Outlook.ExplorerEvents_10_SelectionChangeEventHandle(ThisAddIn_SelectionChanged);

> The reason of using explorer.SelectionChange is to catch EntryIDs of the
> appointments to be deleted.

> The Email problem has been fixed in Outlook 2007 by replacing
> SelectionChange with BeforeItemMove event.

> What is the feasible solution for 2003?

> I'll start a new thread.

> "Jason" <a@a.com> wrote in message
> news:%23zkIOkttJHA.4592@TK2MSFTNGP06.phx.gbl...
> > Yes you are right. The problem only occurs when user clicks the Outbox
> > folder then create a new mail. No problem if user has not highlighted the
> > Outbox.
>

>> Once the mail is stalled, no matter how many times you click Send and
> > Receive button, it will stay there forever, even after user move to
> > other folder or restart Outlook. You have to delete it, and create an new
> > mail.
>

>> What can I do then? Tell user not to select Outbox, or unselect the
> > Outbox programmatically if user does that?
 
J

Jason

It works! Thanks Ken. You are genius.
<kenslovak@mvps.org> wrote in message

news:eMSgk74tJHA.248@TK2MSFTNGP06.phx.gbl...
> Please do not start new threads for the same problem. It just confuses
> things.

> If items in the Outbox are messed with using code then they won't go out.
> That is true of all Outlook versions. So the simple answer is don't do
> that. There's no need to do it, so don't.

> If the ActiveExplorer.CurrentFolder is Outbox just don't handle
> SelectionChange() there. If it's not Outbox you can safely handle
> SelectionChange(). Since BeforeFolderSwitch() will fire before the folder
> in the Explorer is switched to Outbox you will know when that happens. So
> just remove the SelectionChange() handler then and reinstate it when the
> folder isn't Outbox.

> >

>

> "Jason" <a@a.com> wrote in message
> news:OGKSLy4tJHA.496@TK2MSFTNGP06.phx.gbl...
> > Now the problem of email won't go out also occurs on Outlook 2003. So it
> > is not 2007 specific.
>

>> After comment out the explorer.SelectionChange, emailing resumes normal.
>

>> explorer.SelectionChange +=
> > new
> > Outlook.ExplorerEvents_10_SelectionChangeEventHandle(ThisAddIn_SelectionChanged);
>

>> The reason of using explorer.SelectionChange is to catch EntryIDs of the
> > appointments to be deleted.
>

>> The Email problem has been fixed in Outlook 2007 by replacing
> > SelectionChange with BeforeItemMove event.
>

>> What is the feasible solution for 2003?
>

>> I'll start a new thread.
>

>
>> "Jason" <a@a.com> wrote in message
> > news:%23zkIOkttJHA.4592@TK2MSFTNGP06.phx.gbl...
> >> Yes you are right. The problem only occurs when user clicks the Outbox
> >> folder then create a new mail. No problem if user has not highlighted
> >> the Outbox.
> >
>>> Once the mail is stalled, no matter how many times you click Send and
> >> Receive button, it will stay there forever, even after user move to
> >> other folder or restart Outlook. You have to delete it, and create an
> >> new mail.
> >
>>> What can I do then? Tell user not to select Outbox, or unselect the
> >> Outbox programmatically if user does that?

>
 
J

Jason

The problem of Email won't go out appears in one VM for Outlook 2007. No

problem in dev machine since we replaced the ActiveExplorer.SelectionChange

with BeforeItemMove event. Now the suspect is

Application.Inspectors.NewInspector event. What we really need is the

calendar item open event (or better, the Read event to handle in place

input). Is there any way to catch the calendar item Open/Read event without

intercepting the NewInspector event? Please advise how to.

"Jason" <a@a.com> wrote in message

news:eHg$dl$tJHA.4928@TK2MSFTNGP03.phx.gbl...
> It works! Thanks Ken. You are genius.

> " - " <kenslovak@mvps.org> wrote in message
> news:eMSgk74tJHA.248@TK2MSFTNGP06.phx.gbl...
> > Please do not start new threads for the same problem. It just confuses
> > things.
>

>> If items in the Outbox are messed with using code then they won't go out.
> > That is true of all Outlook versions. So the simple answer is don't do
> > that. There's no need to do it, so don't.
>

>> If the ActiveExplorer.CurrentFolder is Outbox just don't handle
> > SelectionChange() there. If it's not Outbox you can safely handle
> > SelectionChange(). Since BeforeFolderSwitch() will fire before the folder
> > in the Explorer is switched to Outbox you will know when that happens. So
> > just remove the SelectionChange() handler then and reinstate it when the
> > folder isn't Outbox.
>

>> > >

> >

>

>
>
>
>
>
>> "Jason" <a@a.com> wrote in message
> > news:OGKSLy4tJHA.496@TK2MSFTNGP06.phx.gbl...
> >> Now the problem of email won't go out also occurs on Outlook 2003. So it
> >> is not 2007 specific.
> >
>>> After comment out the explorer.SelectionChange, emailing resumes normal.
> >
>>> explorer.SelectionChange +=
> >> new
> >> Outlook.ExplorerEvents_10_SelectionChangeEventHandle(ThisAddIn_SelectionChanged);
> >
>>> The reason of using explorer.SelectionChange is to catch EntryIDs of the
> >> appointments to be deleted.
> >
>>> The Email problem has been fixed in Outlook 2007 by replacing
> >> SelectionChange with BeforeItemMove event.
> >
>>> What is the feasible solution for 2003?
> >
>>> I'll start a new thread.
> >
>>
>>> "Jason" <a@a.com> wrote in message
> >> news:%23zkIOkttJHA.4592@TK2MSFTNGP06.phx.gbl...
> >>> Yes you are right. The problem only occurs when user clicks the Outbox
> >>> folder then create a new mail. No problem if user has not highlighted
> >>> the Outbox.
> >>
>>>> Once the mail is stalled, no matter how many times you click Send and
> >>> Receive button, it will stay there forever, even after user move to
> >>> other folder or restart Outlook. You have to delete it, and create an
> >>> new mail.
> >>
>>>> What can I do then? Tell user not to select Outbox, or unselect the
> >>> Outbox programmatically if user does that?

> >


>
 
K

Ken Slovak - [MVP - Outlook]

If you don't want to handle NewInspector() you would have to follow the

Selection of ActiveExplorer() and instantiate event handling objects for

each Selection member. Then you can handle the Open(), Close(), Read(), etc.

events for those items.

"Jason" <a@a.com> wrote in message

news:%23eya8HpwJHA.1088@TK2MSFTNGP04.phx.gbl...
> The problem of Email won't go out appears in one VM for Outlook 2007. No
> problem in dev machine since we replaced the
> ActiveExplorer.SelectionChange with BeforeItemMove event. Now the suspect
> is Application.Inspectors.NewInspector event. What we really need is the
> calendar item open event (or better, the Read event to handle in place
> input). Is there any way to catch the calendar item Open/Read event
> without intercepting the NewInspector event? Please advise how to.
>
 
Status
Not open for further replies.
Similar threads
Thread starter Title Forum Replies Date
B Add-in "always enabled" but Outlook 13 won't open Using Outlook 7
F Add-In Tab won't display in Outlook 2010 Ribbon Using Outlook 1
M OL2007 Add-in won't install on OL2010 Outlook VBA and Custom Forms 1
P Shortcut Pane - add shortcut to Office365 group mailbox Using Outlook 1
B Add ComboBox Value to Body of Email Outlook VBA and Custom Forms 1
G How to add a folder shortcut to outlook quick access toolbar? Using Outlook 6
G Add to Outlook Contacts - Point to non-default contacts folder Using Outlook 0
M Automatically add senders first name to a greeting Outlook VBA and Custom Forms 1
C Add Form to Appointments Received, Automatically Outlook VBA and Custom Forms 6
O Outlook tasks - Add text column with multiple lines Using Outlook 3
W April 2020 Office 365 Update - Add-Ons fail after Office 365 Update Using Outlook 6
B Task Filter Not Working When I add too many criteria Using Outlook 0
D Add date next to day name in Outlook Today calendar view Using Outlook 1
D iCloud Add-in not working in Outlook 2013 and Outlook 2016 After Windows Upgrade & iCloud Upgrade Using Outlook 2
P Add Paste Unformatted to QAT Using Outlook 1
M Ignore slow add-ins Using Outlook 0
B Add Prefix text to Subject Line Using Outlook 1
Jennifer Murphy Add birthdays to calendar Using Outlook 7
Z Add text to auto-forwarded e-mail Outlook VBA and Custom Forms 4
P Add, remove, & reorder folder pane Using Outlook 6
L Tired of Outlook disabling Adobe PDF Creator add-in Using Outlook 1
R Add 'Company' to Select Names Form Using Outlook 1
A Outlook 2016 Web add-in missing on some machines Using Outlook 9
P Syncing problems with add-ins Using Outlook 3
Mark Foley Cannot enable add-in in outlook 2010 Using Outlook 0
BretAB Is it possible to add a lookup field to a Message form? Outlook VBA and Custom Forms 4
J Add an Attachment Using an Array and Match first 17 Letters to Matching Template .oft to Send eMail Outlook VBA and Custom Forms 2
iwshim outlook 2013 - I cannot see the "Manage Add-ins" Using Outlook 2
A Add multiple servers "on behalf of" email to "safe senders" list. Using Outlook 1
S Add Exchange Account as Secondary to Existing PST? Exchange Server Administration 1
C Macro to add multiple recipients to message Outlook VBA and Custom Forms 3
A Add to Outlook Contacts from email - default view Outlook VBA and Custom Forms 1
P Add a contact to the New Task in Outlook 2016 Using Outlook 2
e_a_g_l_e_p_i Is there a way to add something that is in the "Format Text" tab to the "basic Text" on the message tab Using Outlook 1
B When working on emails in a certain folder, when I hit reply or reply all, I would like it re always reply all and add an email address to send to Outlook VBA and Custom Forms 3
M Macro to add date/time stamp to subject Outlook VBA and Custom Forms 4
O Outlook on Android - add BCC Using Outlook 2
J Execute Add-In Button from VBA Outlook 2016 Outlook VBA and Custom Forms 1
S Example VBA Macro - To Conditionally Change the From Account and Add a BCC Address on Emails Outlook VBA and Custom Forms 11
B When I add more search strings to RULES, it is not processing them Using Outlook 3
D Add Tetxbox at form open Outlook VBA and Custom Forms 1
Andrew Quirl Open attachment, manipulate without add-on program? Outlook VBA and Custom Forms 5
B Searching for a Add-In Using Outlook 3
J Add Fillable Fields to Existing Template Outlook VBA and Custom Forms 1
J vb to c# for Outlook add-in. Using Outlook 0
S Send email via SMTP - use transport rules to add to senders inbox (then rule to move to sent items Exchange Server Administration 1
R Outlook add-in to create new contact from an email. Using Outlook 0
twofivepie GTD Netcentrics add-in for 2016 Outlook VBA and Custom Forms 13
D Add all meeting rooms to the meeting request by default Outlook VBA and Custom Forms 0
A add birthday to outlook contacts Using Outlook 1

Similar threads

Top