467,219 Members | 1,221 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

Post your question to a community of 467,219 developers. It's quick & easy.

Slow opening of outlook

Hi

When I open a new outlook email from vb.net, sometimes outlook is very slow
to appear or occasionally outlook freezes completely. I am targeting mixed
office2000/xp environments so I am using the office2000 interop dlls
generated by vs.net by adding office 2000 com reference.

Any one else noticed this problem when targeting office2000/xp mixed
environments? Is there a better, more robust way to do this? Am I better off
using late binding?

Thanks

Regards


Nov 20 '05 #1
  • viewed: 2489
Share:
10 Replies
Do you have MS Messenger running ?

"John" <jo**@nospam.infovis.co.uk> wrote in message
news:#M**************@tk2msftngp13.phx.gbl...
Hi

When I open a new outlook email from vb.net, sometimes outlook is very slow to appear or occasionally outlook freezes completely. I am targeting mixed
office2000/xp environments so I am using the office2000 interop dlls
generated by vs.net by adding office 2000 com reference.

Any one else noticed this problem when targeting office2000/xp mixed
environments? Is there a better, more robust way to do this? Am I better off using late binding?

Thanks

Regards

Nov 20 '05 #2
Nope.

Regards

"Marcel" <so*********@spam.com> wrote in message
news:e8*************@tk2msftngp13.phx.gbl...
Do you have MS Messenger running ?

"John" <jo**@nospam.infovis.co.uk> wrote in message
news:#M**************@tk2msftngp13.phx.gbl...
Hi

When I open a new outlook email from vb.net, sometimes outlook is very

slow
to appear or occasionally outlook freezes completely. I am targeting mixed office2000/xp environments so I am using the office2000 interop dlls
generated by vs.net by adding office 2000 com reference.

Any one else noticed this problem when targeting office2000/xp mixed
environments? Is there a better, more robust way to do this? Am I better

off
using late binding?

Thanks

Regards


Nov 20 '05 #3
John,
Are you starting Outlook fresh or is it already running? When Outlook is
already running does the same thing happen?

Does this happen "right away" or after using Outlook from VB.NET for awhile?

Are you using System.Runtime.InteropServices.Marshal.ReelaseComO bject on
each Outlook object returned, when you are done with that object?

Are you calling Item.Display to show an item or just connecting and
retrieving & updating information? Does this "slowness" happen with specific
Outlook objects & methods?

Do you have other things running on your computer?

Which version of the OS?

Are you using Exchange Server or internet mode?

Are you getting the "security dialog" that states that someone is accessing
your email? And just not seeing it in time?
In case you don't have it, the following site provides a plethora of
articles on using Outlook from .NET:
http://www.microeye.com/resources/res_outlookvsnet.htm

Using Outlook 2003 with VB.NET & the Office 2003 PIA I have not noticed
Outlook being slow to appear.

Unfortunately I don't have a machine with either office 2000 or Office XP.

Hope this helps
Jay

"John" <jo**@nospam.infovis.co.uk> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
Hi

When I open a new outlook email from vb.net, sometimes outlook is very slow to appear or occasionally outlook freezes completely. I am targeting mixed
office2000/xp environments so I am using the office2000 interop dlls
generated by vs.net by adding office 2000 com reference.

Any one else noticed this problem when targeting office2000/xp mixed
environments? Is there a better, more robust way to do this? Am I better off using late binding?

Thanks

Regards

Nov 20 '05 #4
I am using display to allow user to enter the email and then press send
button to send it. I am not using
System.Runtime.InteropServices.Marshal.ReelaseComO bject. Is there an example
I can see on how to use it?

Thanks

Regards

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:OP**************@tk2msftngp13.phx.gbl...
John,
Are you starting Outlook fresh or is it already running? When Outlook is
already running does the same thing happen?

Does this happen "right away" or after using Outlook from VB.NET for awhile?
Are you using System.Runtime.InteropServices.Marshal.ReelaseComO bject on
each Outlook object returned, when you are done with that object?

Are you calling Item.Display to show an item or just connecting and
retrieving & updating information? Does this "slowness" happen with specific Outlook objects & methods?

Do you have other things running on your computer?

Which version of the OS?

Are you using Exchange Server or internet mode?

Are you getting the "security dialog" that states that someone is accessing your email? And just not seeing it in time?
In case you don't have it, the following site provides a plethora of
articles on using Outlook from .NET:
http://www.microeye.com/resources/res_outlookvsnet.htm

Using Outlook 2003 with VB.NET & the Office 2003 PIA I have not noticed
Outlook being slow to appear.

Unfortunately I don't have a machine with either office 2000 or Office XP.

Hope this helps
Jay

"John" <jo**@nospam.infovis.co.uk> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
Hi

When I open a new outlook email from vb.net, sometimes outlook is very

slow
to appear or occasionally outlook freezes completely. I am targeting mixed office2000/xp environments so I am using the office2000 interop dlls
generated by vs.net by adding office 2000 com reference.

Any one else noticed this problem when targeting office2000/xp mixed
environments? Is there a better, more robust way to do this? Am I better

off
using late binding?

Thanks

Regards


Nov 20 '05 #5
John,
Did you try searching MSDN for ReleaseComObject?

The first link returned looks like a promising example:

http://msdn.microsoft.com/library/de...omateVBNet.asp

The second link is the documentation for the function:

http://msdn.microsoft.com/library/de...bjecttopic.asp

Hope this helps
Jay
"John" <jo**@nospam.infovis.co.uk> wrote in message
news:Ot**************@tk2msftngp13.phx.gbl...
I am using display to allow user to enter the email and then press send
button to send it. I am not using
System.Runtime.InteropServices.Marshal.ReelaseComO bject. Is there an example I can see on how to use it?

Thanks

Regards

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:OP**************@tk2msftngp13.phx.gbl...
John,
Are you starting Outlook fresh or is it already running? When Outlook is
already running does the same thing happen?

Does this happen "right away" or after using Outlook from VB.NET for

awhile?

Are you using System.Runtime.InteropServices.Marshal.ReelaseComO bject on
each Outlook object returned, when you are done with that object?

Are you calling Item.Display to show an item or just connecting and
retrieving & updating information? Does this "slowness" happen with

specific
Outlook objects & methods?

Do you have other things running on your computer?

Which version of the OS?

Are you using Exchange Server or internet mode?

Are you getting the "security dialog" that states that someone is

accessing
your email? And just not seeing it in time?
In case you don't have it, the following site provides a plethora of
articles on using Outlook from .NET:
http://www.microeye.com/resources/res_outlookvsnet.htm

Using Outlook 2003 with VB.NET & the Office 2003 PIA I have not noticed
Outlook being slow to appear.

Unfortunately I don't have a machine with either office 2000 or Office XP.

Hope this helps
Jay

"John" <jo**@nospam.infovis.co.uk> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
Hi

When I open a new outlook email from vb.net, sometimes outlook is
very slow
to appear or occasionally outlook freezes completely. I am targeting mixed office2000/xp environments so I am using the office2000 interop dlls
generated by vs.net by adding office 2000 com reference.

Any one else noticed this problem when targeting office2000/xp mixed
environments? Is there a better, more robust way to do this? Am I

better off
using late binding?

Thanks

Regards



Nov 20 '05 #6
Hi

Not sure how to relate the access example with outlook. Tried to mimic it
but no luck and same error. Isn't there an outlook example around, creating
a new email then display and then cleanup?

Regards

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:uO**************@TK2MSFTNGP12.phx.gbl...
John,
Did you try searching MSDN for ReleaseComObject?

The first link returned looks like a promising example:

http://msdn.microsoft.com/library/de...omateVBNet.asp
The second link is the documentation for the function:

http://msdn.microsoft.com/library/de...bjecttopic.asp
Hope this helps
Jay
"John" <jo**@nospam.infovis.co.uk> wrote in message
news:Ot**************@tk2msftngp13.phx.gbl...
I am using display to allow user to enter the email and then press send
button to send it. I am not using
System.Runtime.InteropServices.Marshal.ReelaseComO bject. Is there an

example
I can see on how to use it?

Thanks

Regards

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:OP**************@tk2msftngp13.phx.gbl...
John,
Are you starting Outlook fresh or is it already running? When Outlook is already running does the same thing happen?

Does this happen "right away" or after using Outlook from VB.NET for

awhile?

Are you using System.Runtime.InteropServices.Marshal.ReelaseComO bject on each Outlook object returned, when you are done with that object?

Are you calling Item.Display to show an item or just connecting and
retrieving & updating information? Does this "slowness" happen with

specific
Outlook objects & methods?

Do you have other things running on your computer?

Which version of the OS?

Are you using Exchange Server or internet mode?

Are you getting the "security dialog" that states that someone is

accessing
your email? And just not seeing it in time?
In case you don't have it, the following site provides a plethora of
articles on using Outlook from .NET:
http://www.microeye.com/resources/res_outlookvsnet.htm

Using Outlook 2003 with VB.NET & the Office 2003 PIA I have not noticed Outlook being slow to appear.

Unfortunately I don't have a machine with either office 2000 or Office

XP.
Hope this helps
Jay

"John" <jo**@nospam.infovis.co.uk> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
> Hi
>
> When I open a new outlook email from vb.net, sometimes outlook is very slow
> to appear or occasionally outlook freezes completely. I am targeting

mixed
> office2000/xp environments so I am using the office2000 interop dlls
> generated by vs.net by adding office 2000 com reference.
>
> Any one else noticed this problem when targeting office2000/xp mixed
> environments? Is there a better, more robust way to do this? Am I better off
> using late binding?
>
> Thanks
>
> Regards
>
>
>
>



Nov 20 '05 #7
John,
How does that saying go: Give a man a fish he eats for a day, teach a man to
fix he eats for live? :-)

The Access example should show you enough of the Concept of working with
Office Automation & ReleaseComObject when combined with the Outlook VBA Help
you should be able to create a working example! As I find VB6 & VBA examples
come are translated almost 1 for 1, the few exceptions to the rule I find
are easy to remember.
but no luck and same error. Isn't there an outlook example around, creating a new email then display and then cleanup? Unfortunately I am not setup to test Outlook 2000 automation with .NET.
However! others have used Outlook 2000 from VB.NET with success, have you
reviewed the info at:

http://www.microeye.com/resources/res_outlookvsnet.htm

There is at least one article that specifically deals specifically with
Outlook 2000!

Here is an example of "creating a new email, then display, and then
cleanup":

Imports System.Runtime.InteropServices
Dim app As New Outlook.Application
Dim ns As Outlook.NameSpace
ns = app.GetNamespace("MAPI")
ns.Logon()
Dim mailItem As Outlook.MailItem
mailItem = DirectCast(app.CreateItem(Outlook.OlItemType.olMai lItem),
Outlook.MailItem)
mailItem.Display(False)

Marshal.ReleaseComObject(mailItem)
ns.Logoff()
Marshal.ReleaseComObject(ns)
Marshal.ReleaseComObject(app)
Return

I am checking with my fellow Outlook MVPs on why mailItem.Display(True)
leaves the window on the screen.

Hope this helps
Jay
"John" <jo**@nospam.infovis.co.uk> wrote in message
news:%2****************@tk2msftngp13.phx.gbl... Hi

Not sure how to relate the access example with outlook. Tried to mimic it
but no luck and same error. Isn't there an outlook example around, creating a new email then display and then cleanup?

Regards

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:uO**************@TK2MSFTNGP12.phx.gbl...
John,
Did you try searching MSDN for ReleaseComObject?

The first link returned looks like a promising example:

http://msdn.microsoft.com/library/de...omateVBNet.asp

The second link is the documentation for the function:

http://msdn.microsoft.com/library/de...bjecttopic.asp

Hope this helps
Jay
"John" <jo**@nospam.infovis.co.uk> wrote in message
news:Ot**************@tk2msftngp13.phx.gbl...
I am using display to allow user to enter the email and then press send button to send it. I am not using
System.Runtime.InteropServices.Marshal.ReelaseComO bject. Is there an

example
I can see on how to use it?

Thanks

Regards

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message news:OP**************@tk2msftngp13.phx.gbl...
> John,
> Are you starting Outlook fresh or is it already running? When Outlook is
> already running does the same thing happen?
>
> Does this happen "right away" or after using Outlook from VB.NET for
awhile?
>
> Are you using
System.Runtime.InteropServices.Marshal.ReelaseComO bject
on > each Outlook object returned, when you are done with that object?
>
> Are you calling Item.Display to show an item or just connecting and
> retrieving & updating information? Does this "slowness" happen with
specific
> Outlook objects & methods?
>
> Do you have other things running on your computer?
>
> Which version of the OS?
>
> Are you using Exchange Server or internet mode?
>
> Are you getting the "security dialog" that states that someone is
accessing
> your email? And just not seeing it in time?
>
>
> In case you don't have it, the following site provides a plethora of
> articles on using Outlook from .NET:
> http://www.microeye.com/resources/res_outlookvsnet.htm
>
> Using Outlook 2003 with VB.NET & the Office 2003 PIA I have not noticed > Outlook being slow to appear.
>
> Unfortunately I don't have a machine with either office 2000 or
Office XP.
>
> Hope this helps
> Jay
>
> "John" <jo**@nospam.infovis.co.uk> wrote in message
> news:%2****************@tk2msftngp13.phx.gbl...
> > Hi
> >
> > When I open a new outlook email from vb.net, sometimes outlook is

very
> slow
> > to appear or occasionally outlook freezes completely. I am

targeting mixed
> > office2000/xp environments so I am using the office2000 interop dlls > > generated by vs.net by adding office 2000 com reference.
> >
> > Any one else noticed this problem when targeting office2000/xp mixed > > environments? Is there a better, more robust way to do this? Am I

better
> off
> > using late binding?
> >
> > Thanks
> >
> > Regards
> >
> >
> >
> >
>
>



Nov 20 '05 #8
John,
Are you using Word as the Editor in Outlook?

There seems to be a problem closing Word when used as the Editor in Outlook,
try the following code to close Word.

Something like:
Dim app As New Outlook.Application
Dim mailItem As Outlook.MailItem
mailItem = DirectCast(app.CreateItem(Outlook.OlItemType.olMai lItem),
Outlook.MailItem)
Dim objInsp As Outlook.Inspector
objInsp = mailItem.GetInspector()

mailItem.Display(True)

Marshal.ReleaseComObject(objInsp)

Marshal.ReleaseComObject(mailItem)
Marshal.ReleaseComObject(app)

Note, the dialog is not displayed modally, but its left open for you to fill
out & send...

Hope this helps
Jay

"John" <jo**@nospam.infovis.co.uk> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
Hi

Not sure how to relate the access example with outlook. Tried to mimic it
but no luck and same error. Isn't there an outlook example around, creating a new email then display and then cleanup?

Regards

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:uO**************@TK2MSFTNGP12.phx.gbl...
John,
Did you try searching MSDN for ReleaseComObject?

The first link returned looks like a promising example:

http://msdn.microsoft.com/library/de...omateVBNet.asp

The second link is the documentation for the function:

http://msdn.microsoft.com/library/de...bjecttopic.asp

Hope this helps
Jay
"John" <jo**@nospam.infovis.co.uk> wrote in message
news:Ot**************@tk2msftngp13.phx.gbl...
I am using display to allow user to enter the email and then press send button to send it. I am not using
System.Runtime.InteropServices.Marshal.ReelaseComO bject. Is there an

example
I can see on how to use it?

Thanks

Regards

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message news:OP**************@tk2msftngp13.phx.gbl...
> John,
> Are you starting Outlook fresh or is it already running? When Outlook is
> already running does the same thing happen?
>
> Does this happen "right away" or after using Outlook from VB.NET for
awhile?
>
> Are you using
System.Runtime.InteropServices.Marshal.ReelaseComO bject
on > each Outlook object returned, when you are done with that object?
>
> Are you calling Item.Display to show an item or just connecting and
> retrieving & updating information? Does this "slowness" happen with
specific
> Outlook objects & methods?
>
> Do you have other things running on your computer?
>
> Which version of the OS?
>
> Are you using Exchange Server or internet mode?
>
> Are you getting the "security dialog" that states that someone is
accessing
> your email? And just not seeing it in time?
>
>
> In case you don't have it, the following site provides a plethora of
> articles on using Outlook from .NET:
> http://www.microeye.com/resources/res_outlookvsnet.htm
>
> Using Outlook 2003 with VB.NET & the Office 2003 PIA I have not noticed > Outlook being slow to appear.
>
> Unfortunately I don't have a machine with either office 2000 or
Office XP.
>
> Hope this helps
> Jay
>
> "John" <jo**@nospam.infovis.co.uk> wrote in message
> news:%2****************@tk2msftngp13.phx.gbl...
> > Hi
> >
> > When I open a new outlook email from vb.net, sometimes outlook is

very
> slow
> > to appear or occasionally outlook freezes completely. I am

targeting mixed
> > office2000/xp environments so I am using the office2000 interop dlls > > generated by vs.net by adding office 2000 com reference.
> >
> > Any one else noticed this problem when targeting office2000/xp mixed > > environments? Is there a better, more robust way to do this? Am I

better
> off
> > using late binding?
> >
> > Thanks
> >
> > Regards
> >
> >
> >
> >
>
>



Nov 20 '05 #9

Thanks for that. It works fine the first time but calling the code second
time gives the following error;

Unhandled Exception: System.Reflection.TargetInvocationException: Exception
has been thrown by the target of an invocation. --->
System.Runtime.InteropServices.InvalidComObjectExc eption: COM object that
has been separated from its underlying RCW can not be used.
at Outlook.ApplicationEvents_EventProvider..ctor(Obje ct )

I am using the below code and the error comes on the 'OutlookApp = New
Outlook.Application' line. Any ideas what I am missing?

Thanks

Regards

= Code below =======================

Imports System.Runtime.InteropServices

Public Class clsOfficeWrapper
Private WithEvents OutlookApp As Outlook.Application
Private WithEvents em As Outlook.MailItem

Public Sub NewEmail(ByVal EmailTemplate As String, ByVal SendTo As String)
Dim ns As Outlook.NameSpace

OutlookApp = New Outlook.Application ' <=== This lines give the
exception second time round
ns = OutlookApp.GetNamespace("MAPI")
ns.Logon()

em = DirectCast(OutlookApp.CreateItemFromTemplate(Email Template),
Outlook.MailItem)
.To = SendTo
.Display(False)

Marshal.ReleaseComObject(em)
ns.Logoff()
Marshal.ReleaseComObject(ns)
Marshal.ReleaseComObject(OutlookApp)
End Sub
....

End Class

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
John,
How does that saying go: Give a man a fish he eats for a day, teach a man to fix he eats for live? :-)

The Access example should show you enough of the Concept of working with
Office Automation & ReleaseComObject when combined with the Outlook VBA Help you should be able to create a working example! As I find VB6 & VBA examples come are translated almost 1 for 1, the few exceptions to the rule I find
are easy to remember.
but no luck and same error. Isn't there an outlook example around, creating
a new email then display and then cleanup?

Unfortunately I am not setup to test Outlook 2000 automation with .NET.
However! others have used Outlook 2000 from VB.NET with success, have you
reviewed the info at:

http://www.microeye.com/resources/res_outlookvsnet.htm

There is at least one article that specifically deals specifically with
Outlook 2000!

Here is an example of "creating a new email, then display, and then
cleanup":

Imports System.Runtime.InteropServices
Dim app As New Outlook.Application
Dim ns As Outlook.NameSpace
ns = app.GetNamespace("MAPI")
ns.Logon()
Dim mailItem As Outlook.MailItem
mailItem =

DirectCast(app.CreateItem(Outlook.OlItemType.olMai lItem), Outlook.MailItem)
mailItem.Display(False)

Marshal.ReleaseComObject(mailItem)
ns.Logoff()
Marshal.ReleaseComObject(ns)
Marshal.ReleaseComObject(app)
Return

I am checking with my fellow Outlook MVPs on why mailItem.Display(True)
leaves the window on the screen.

Hope this helps
Jay
"John" <jo**@nospam.infovis.co.uk> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
Hi

Not sure how to relate the access example with outlook. Tried to mimic it
but no luck and same error. Isn't there an outlook example around,

creating
a new email then display and then cleanup?

Regards

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message news:uO**************@TK2MSFTNGP12.phx.gbl...
John,
Did you try searching MSDN for ReleaseComObject?

The first link returned looks like a promising example:

http://msdn.microsoft.com/library/de...omateVBNet.asp

The second link is the documentation for the function:

http://msdn.microsoft.com/library/de...bjecttopic.asp

Hope this helps
Jay
"John" <jo**@nospam.infovis.co.uk> wrote in message
news:Ot**************@tk2msftngp13.phx.gbl...
> I am using display to allow user to enter the email and then press send > button to send it. I am not using
> System.Runtime.InteropServices.Marshal.ReelaseComO bject. Is there an
example
> I can see on how to use it?
>
> Thanks
>
> Regards
>
> "Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in

message
> news:OP**************@tk2msftngp13.phx.gbl...
> > John,
> > Are you starting Outlook fresh or is it already running? When Outlook
is
> > already running does the same thing happen?
> >
> > Does this happen "right away" or after using Outlook from VB.NET for > awhile?
> >
> > Are you using

System.Runtime.InteropServices.Marshal.ReelaseComO bject
on
> > each Outlook object returned, when you are done with that object?
> >
> > Are you calling Item.Display to show an item or just connecting and > > retrieving & updating information? Does this "slowness" happen with > specific
> > Outlook objects & methods?
> >
> > Do you have other things running on your computer?
> >
> > Which version of the OS?
> >
> > Are you using Exchange Server or internet mode?
> >
> > Are you getting the "security dialog" that states that someone is
> accessing
> > your email? And just not seeing it in time?
> >
> >
> > In case you don't have it, the following site provides a plethora of > > articles on using Outlook from .NET:
> > http://www.microeye.com/resources/res_outlookvsnet.htm
> >
> > Using Outlook 2003 with VB.NET & the Office 2003 PIA I have not

noticed
> > Outlook being slow to appear.
> >
> > Unfortunately I don't have a machine with either office 2000 or

Office XP.
> >
> > Hope this helps
> > Jay
> >
> > "John" <jo**@nospam.infovis.co.uk> wrote in message
> > news:%2****************@tk2msftngp13.phx.gbl...
> > > Hi
> > >
> > > When I open a new outlook email from vb.net, sometimes outlook is very
> > slow
> > > to appear or occasionally outlook freezes completely. I am targeting > mixed
> > > office2000/xp environments so I am using the office2000 interop dlls > > > generated by vs.net by adding office 2000 com reference.
> > >
> > > Any one else noticed this problem when targeting office2000/xp mixed > > > environments? Is there a better, more robust way to do this? Am I better
> > off
> > > using late binding?
> > >
> > > Thanks
> > >
> > > Regards
> > >
> > >
> > >
> > >
> >
> >
>
>



Nov 20 '05 #10
I am not using word as editor.

Thanks

Regards
"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:e9**************@TK2MSFTNGP11.phx.gbl...
John,
Are you using Word as the Editor in Outlook?

There seems to be a problem closing Word when used as the Editor in Outlook, try the following code to close Word.

Something like:
Dim app As New Outlook.Application
Dim mailItem As Outlook.MailItem
mailItem = DirectCast(app.CreateItem(Outlook.OlItemType.olMai lItem), Outlook.MailItem)
Dim objInsp As Outlook.Inspector
objInsp = mailItem.GetInspector()

mailItem.Display(True)

Marshal.ReleaseComObject(objInsp)

Marshal.ReleaseComObject(mailItem)
Marshal.ReleaseComObject(app)

Note, the dialog is not displayed modally, but its left open for you to fill out & send...

Hope this helps
Jay

"John" <jo**@nospam.infovis.co.uk> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
Hi

Not sure how to relate the access example with outlook. Tried to mimic it
but no luck and same error. Isn't there an outlook example around,

creating
a new email then display and then cleanup?

Regards

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message news:uO**************@TK2MSFTNGP12.phx.gbl...
John,
Did you try searching MSDN for ReleaseComObject?

The first link returned looks like a promising example:

http://msdn.microsoft.com/library/de...omateVBNet.asp

The second link is the documentation for the function:

http://msdn.microsoft.com/library/de...bjecttopic.asp

Hope this helps
Jay
"John" <jo**@nospam.infovis.co.uk> wrote in message
news:Ot**************@tk2msftngp13.phx.gbl...
> I am using display to allow user to enter the email and then press send > button to send it. I am not using
> System.Runtime.InteropServices.Marshal.ReelaseComO bject. Is there an
example
> I can see on how to use it?
>
> Thanks
>
> Regards
>
> "Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in

message
> news:OP**************@tk2msftngp13.phx.gbl...
> > John,
> > Are you starting Outlook fresh or is it already running? When Outlook
is
> > already running does the same thing happen?
> >
> > Does this happen "right away" or after using Outlook from VB.NET for > awhile?
> >
> > Are you using

System.Runtime.InteropServices.Marshal.ReelaseComO bject
on
> > each Outlook object returned, when you are done with that object?
> >
> > Are you calling Item.Display to show an item or just connecting and > > retrieving & updating information? Does this "slowness" happen with > specific
> > Outlook objects & methods?
> >
> > Do you have other things running on your computer?
> >
> > Which version of the OS?
> >
> > Are you using Exchange Server or internet mode?
> >
> > Are you getting the "security dialog" that states that someone is
> accessing
> > your email? And just not seeing it in time?
> >
> >
> > In case you don't have it, the following site provides a plethora of > > articles on using Outlook from .NET:
> > http://www.microeye.com/resources/res_outlookvsnet.htm
> >
> > Using Outlook 2003 with VB.NET & the Office 2003 PIA I have not

noticed
> > Outlook being slow to appear.
> >
> > Unfortunately I don't have a machine with either office 2000 or

Office XP.
> >
> > Hope this helps
> > Jay
> >
> > "John" <jo**@nospam.infovis.co.uk> wrote in message
> > news:%2****************@tk2msftngp13.phx.gbl...
> > > Hi
> > >
> > > When I open a new outlook email from vb.net, sometimes outlook is very
> > slow
> > > to appear or occasionally outlook freezes completely. I am targeting > mixed
> > > office2000/xp environments so I am using the office2000 interop dlls > > > generated by vs.net by adding office 2000 com reference.
> > >
> > > Any one else noticed this problem when targeting office2000/xp mixed > > > environments? Is there a better, more robust way to do this? Am I better
> > off
> > > using late binding?
> > >
> > > Thanks
> > >
> > > Regards
> > >
> > >
> > >
> > >
> >
> >
>
>



Nov 20 '05 #11

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Jawahar Rajan | last post: by
reply views Thread by Dhammika | last post: by
12 posts views Thread by Neil | last post: by
2 posts views Thread by Rocky A | last post: by
1 post views Thread by John | last post: by
50 posts views Thread by diffuser78@gmail.com | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.