View Single Post
  #4  
Old June 1st 06, 09:20 PM posted to microsoft.public.outlook.program_vba
Eric Legault [MVP - Outlook]
external usenet poster
 
Posts: 830
Default Outlook view control and one process

Why would multiple instancess of the Outlook.exe process matter? What
conflicts are you experiencing with your OVC if one or more instances of
Outlook.exe are running? What exactly are you trying to do with the OVC?

--
Eric Legault (Outlook MVP, MCDBA, MCTS: Messaging & Collaboration)
Try Picture Attachments Wizard for Outlook:
http://www.collaborativeinnovations.ca
Blog: http://blogs.officezealot.com/legault/


"CannedWolf" wrote:

I understand that. My question is not about functionality. I am
intimately familiar with the functionality.

I know that I can programatically force multiple instances of a single
application (depending on the application). It may be the full version
of an application of a partial version of the application - that is
inconsequential.

I need to isolate the Outlook.exe process that OVC uses and keep it
separate from the Outlook.exe process that the outlook client uses. Is
this possible? If so, what is the best method of doing so?

Thanks
-Steve


Eric wrote:
As soon as the OVC is instantiated (runtime AND design time), the Outlook.exe
process will run, although there will be no visual Outlook window (but any
Reminders may pop up!). There's no way around this - it's effectively a
window into an instance of Outlook, not a completely separate application.

--
Eric Legault (Outlook MVP, MCDBA, MCTS: Messaging & Collaboration)
Try Picture Attachments Wizard for Outlook:
http://www.collaborativeinnovations.ca
Blog: http://blogs.officezealot.com/legault/


" wrote:

Hello -

We have run into an issue here where an add-in that was written using
VSTO2005 for Outlook is running into a conflict with OVC if OVC and the
Outlook Client are both running at the same time. It appears to be
because they share the same process.

I won't bore you with too many details but, we are running Office 2003
pro sp2 and have all the prerequisites for the add-in to function
properly (which it does) as long as you are accessing it from either
OVC or the client... not both.

Additionally, if the Outlook client is not running, OVC does not
instantiate the add-in. Is this expected behavior?

Is there a way to force OVC to use it's own explorer process?

Thoughts welcome.

Thanks in advance
-Steve




Ads