Hi,
I originally posted this under Word Programming, but I've not had any
response, so I thought I should try my luck with the friendly Outlook
Experts...

I've managed to pull together this code which tests whether Word is used as
the e-mail editor by Outlook (all Office 2003). Running the code from Word,
it appears to work well, except that if it had to open its own Outlook
application (i.e. if Outlook was NOT running at the start) it is supposed to
Quit Outlook with the
olApp.Quit line. But at the end I still have a running Outlook.exe process
in my task manager! Even more strange is that if I run the code a second
time it can't use the existing Outlook application and enters the "If Err
0 Then" loop, so it's as if Outlook was closed, but stayed in the
TaskManager...

Furthermore, if I then start Outlook from the start menu, a second
Outlook.exe appears in the TaskManager and the new Outlook hangs with a
white, empty window!

Why doesn't Outlook quit with this code?

Also, is there an easier way to do this by interogating the Outlook settings
in the registry, thus completely avoiding having to open Outlook?

Many thanks. Here's the code (all in a Word VBA module):

Sub CallTestOutlook()
Dim WordIsUsedByOutlook As String

If TestOutlook = True Then
WordIsUsedByOutlook = "IS"
Else
WordIsUsedByOutlook = "IS NOT"
End If

MsgBox "Word " & WordIsUsedByOutlook & " used by Outlook."
End Sub

Function TestOutlook() As Boolean
Dim olApp As Outlook.Application
Dim olMail As Outlook.MailItem
Dim olInspector As Outlook.Inspector
Dim bStarted As Boolean

'Get a handle on the Outlook Application (if it is running)
On Error Resume Next
Set olApp = GetObject(, "Outlook.Application")

'If Outlook is not running then start Outlook
If Err 0 Then
On Error GoTo ErrorHandler
Set olApp = CreateObject("Outlook.Application")
bStarted = True
Else
On Error GoTo ErrorHandler
End If

'Create a MailItem and and Inspector for it
Set olMail = olApp.CreateItem(olMailItem)
Set olInspector = olMail.GetInspector

'Test whether Word is used by Outlook as e-mail editor
If olInspector.IsWordMail Then
TestOutlook = True
Else
TestOutlook = False
End If

Set olInspector = Nothing
Set olMail = Nothing

'Close Outlook if it was started by this macro.
If bStarted Then
olApp.Quit
End If

Set olApp = Nothing
Exit Function
ErrorHandler:
MsgBox "Error " & Err.Number & " " & Err.Description
End Function


Cheers
Rich

I fail to see why Outlook wouldn't quit, see if adding a line like this
would help:

olApp.Session.Logon "", "", False, False

'Create a MailItem and and Inspector for it
Set olMail = olApp.CreateItem(olMailItem)

You can check at
HKCU\Software\Microsoft\Office\11.0\Outlook\Option s\Mail\UseWordMail (a
REG_DWORD, 1 = yes). The "11.0" is specific to Outlook 2003.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Rich007" wrote in message
news
Hi,
I originally posted this under Word Programming, but I've not had any
response, so I thought I should try my luck with the friendly Outlook
Experts...

I've managed to pull together this code which tests whether Word is used
as
the e-mail editor by Outlook (all Office 2003). Running the code from
Word,
it appears to work well, except that if it had to open its own Outlook
application (i.e. if Outlook was NOT running at the start) it is supposed
to
Quit Outlook with the
olApp.Quit line. But at the end I still have a running Outlook.exe
process
in my task manager! Even more strange is that if I run the code a second
time it can't use the existing Outlook application and enters the "If Err

0 Then" loop, so it's as if Outlook was closed, but stayed in the
TaskManager...

Furthermore, if I then start Outlook from the start menu, a second
Outlook.exe appears in the TaskManager and the new Outlook hangs with a
white, empty window!

Why doesn't Outlook quit with this code?

Also, is there an easier way to do this by interogating the Outlook
settings
in the registry, thus completely avoiding having to open Outlook?

Many thanks. Here's the code (all in a Word VBA module):

Sub CallTestOutlook()
Dim WordIsUsedByOutlook As String

If TestOutlook = True Then
WordIsUsedByOutlook = "IS"
Else
WordIsUsedByOutlook = "IS NOT"
End If

MsgBox "Word " & WordIsUsedByOutlook & " used by Outlook."
End Sub

Function TestOutlook() As Boolean
Dim olApp As Outlook.Application
Dim olMail As Outlook.MailItem
Dim olInspector As Outlook.Inspector
Dim bStarted As Boolean

'Get a handle on the Outlook Application (if it is running)
On Error Resume Next
Set olApp = GetObject(, "Outlook.Application")

'If Outlook is not running then start Outlook
If Err 0 Then
On Error GoTo ErrorHandler
Set olApp = CreateObject("Outlook.Application")
bStarted = True
Else
On Error GoTo ErrorHandler
End If

'Create a MailItem and and Inspector for it
Set olMail = olApp.CreateItem(olMailItem)
Set olInspector = olMail.GetInspector

'Test whether Word is used by Outlook as e-mail editor
If olInspector.IsWordMail Then
TestOutlook = True
Else
TestOutlook = False
End If

Set olInspector = Nothing
Set olMail = Nothing

'Close Outlook if it was started by this macro.
If bStarted Then
olApp.Quit
End If

Set olApp = Nothing
Exit Function
ErrorHandler:
MsgBox "Error " & Err.Number & " " & Err.Description
End Function


Cheers
Rich

Hi Ken, thank you so much for responding.
I tried your suggested extra line of code before creating the MailItem, but
it made no difference. So I tried gradually commenting out lines of code
until Outlook does quit. It appears to be the line:
Set olInspector = olMail.GetInspector
that is causing the issue. If I don't call that line Outlook quits as
ordered. If I do include that line, Outlook stays in the TaskManager. Any
ideas?

Thanks also for providing the registry address. I have never used VBA to
interogate the registry. Would you recommend I use the API route as
described he http://support.microsoft.com/default.aspx/kb/145679 ...or
go down the scripting route as described he
http://vba-corner.livejournal.com/3054.html ?
(these are the first two results I've found in Google).

Thanks again.
Cheers
Rich



"Ken Slovak - [MVP - Outlook]" wrote:

I fail to see why Outlook wouldn't quit, see if adding a line like this
would help:

olApp.Session.Logon "", "", False, False

'Create a MailItem and and Inspector for it
Set olMail = olApp.CreateItem(olMailItem)

You can check at
HKCU\Software\Microsoft\Office\11.0\Outlook\Option s\Mail\UseWordMail (a
REG_DWORD, 1 = yes). The "11.0" is specific to Outlook 2003.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Rich007" wrote in message
news
Hi,
I originally posted this under Word Programming, but I've not had any
response, so I thought I should try my luck with the friendly Outlook
Experts...

I've managed to pull together this code which tests whether Word is used
as
the e-mail editor by Outlook (all Office 2003). Running the code from
Word,
it appears to work well, except that if it had to open its own Outlook
application (i.e. if Outlook was NOT running at the start) it is supposed
to
Quit Outlook with the
olApp.Quit line. But at the end I still have a running Outlook.exe
process
in my task manager! Even more strange is that if I run the code a second
time it can't use the existing Outlook application and enters the "If Err

0 Then" loop, so it's as if Outlook was closed, but stayed in the
TaskManager...

Furthermore, if I then start Outlook from the start menu, a second
Outlook.exe appears in the TaskManager and the new Outlook hangs with a
white, empty window!

Why doesn't Outlook quit with this code?

Also, is there an easier way to do this by interogating the Outlook
settings
in the registry, thus completely avoiding having to open Outlook?

Many thanks. Here's the code (all in a Word VBA module):

Sub CallTestOutlook()
Dim WordIsUsedByOutlook As String

If TestOutlook = True Then
WordIsUsedByOutlook = "IS"
Else
WordIsUsedByOutlook = "IS NOT"
End If

MsgBox "Word " & WordIsUsedByOutlook & " used by Outlook."
End Sub

Function TestOutlook() As Boolean
Dim olApp As Outlook.Application
Dim olMail As Outlook.MailItem
Dim olInspector As Outlook.Inspector
Dim bStarted As Boolean

'Get a handle on the Outlook Application (if it is running)
On Error Resume Next
Set olApp = GetObject(, "Outlook.Application")

'If Outlook is not running then start Outlook
If Err 0 Then
On Error GoTo ErrorHandler
Set olApp = CreateObject("Outlook.Application")
bStarted = True
Else
On Error GoTo ErrorHandler
End If

'Create a MailItem and and Inspector for it
Set olMail = olApp.CreateItem(olMailItem)
Set olInspector = olMail.GetInspector

'Test whether Word is used by Outlook as e-mail editor
If olInspector.IsWordMail Then
TestOutlook = True
Else
TestOutlook = False
End If

Set olInspector = Nothing
Set olMail = Nothing

'Close Outlook if it was started by this macro.
If bStarted Then
olApp.Quit
End If

Set olApp = Nothing
Exit Function
ErrorHandler:
MsgBox "Error " & Err.Number & " " & Err.Description
End Function


Cheers
Rich

In that case try closing the Inspector object when you're done with it,
before you set it to Nothing.

Six of one, half dozen of another as far as reading the registry for that
value. What are you most comfortable with? The only caution is if someone is
running A-V with one of those script stoppers it might prevent the script
access from working.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Rich007" wrote in message
...
Hi Ken, thank you so much for responding.
I tried your suggested extra line of code before creating the MailItem,
but
it made no difference. So I tried gradually commenting out lines of code
until Outlook does quit. It appears to be the line:
Set olInspector = olMail.GetInspector
that is causing the issue. If I don't call that line Outlook quits as
ordered. If I do include that line, Outlook stays in the TaskManager.
Any
ideas?

Thanks also for providing the registry address. I have never used VBA to
interogate the registry. Would you recommend I use the API route as
described he http://support.microsoft.com/default.aspx/kb/145679
...or
go down the scripting route as described he
http://vba-corner.livejournal.com/3054.html ?
(these are the first two results I've found in Google).

Thanks again.
Cheers
Rich

That's it! Thank you Ken.
I needed to close BOTH the Inspector AND the MailItem before calling the
..quit command. All works fine now, although I suspect I will interogate the
registry rather than Outlook itself, since Outlook is slow when it starts
(and if it is open for long enough the calendar reminders can pop up!). I
got the registry query functions working using the API functions provided at
this site:
http://support.microsoft.com/default.aspx/kb/145679

Incidentally, the 2 registry values that sets whether Word is used by
Outlook 2003 are at:
[HKCU\] Software\Microsoft\Office\11.0\Outlook\Options\Mai l
"UseWordMail" is 1 if the "Use Microsoft Office Word 2003 to read Rich Text
e-mail messages" is checked (zero if not).
and
"EditorPreference" which corresponds to the "Use Microsoft Office Word 2003
to edit e-mail messages" checkbox has the following values:
Word is NOT used if EditorPreference is set to either:
' 131072 = HTML/Outlook
' 196610 = Rich Text/Outlook
' 65536 = Plain Text/Outlook

Word IS used if EditorPreference is set to either:
' 196609 = Rich Text/Microsoft Word
' 65537 = Plain Text/Microsoft Word
' 131073 = HTML/Microsoft Word

So my macro for interogating the registry has to test for all these values.

In case anyone else does want to work directly with Outlook to determine
these settings, here is the working function to do it (returns true or false).

Function TestOutlook() As Boolean
Dim olApp As Outlook.Application
Dim olMail As Outlook.MailItem
Dim olInspector As Outlook.Inspector
Dim bStarted As Boolean

'Get a handle on the Outlook Application (if it is running)
On Error Resume Next
Set olApp = GetObject(, "Outlook.Application")

'If Outlook is not running then start Outlook
If Err 0 Then
On Error GoTo ErrorHandler
Set olApp = CreateObject("Outlook.Application")
bStarted = True
Else
On Error GoTo ErrorHandler
End If

'Create a MailItem and an Inspector for it
Set olMail = olApp.CreateItem(olMailItem)
Set olInspector = olMail.GetInspector

'Test whether Word is used by Outlook as e-mail editor
If olInspector.IsWordMail Then
TestOutlook = True 'Function output
Else
TestOutlook = False 'Function output
End If

'Close the Inspector and the MailItem
olInspector.Close (olDiscard) 'MUST HAVE THESE FOR OUTLOOK TO QUIT!
olMail.Close (olDiscard)

'Close Outlook if it was started by this macro.
If bStarted Then
olApp.Quit
End If

'Clean up
Set olInspector = Nothing
Set olMail = Nothing
Set olApp = Nothing
Exit Function
ErrorHandler:
MsgBox "Error " & Err.Number & " " & Err.Description
End Function


Thanks again Ken.
Cheers
Rich

"Ken Slovak - [MVP - Outlook]" wrote:

In that case try closing the Inspector object when you're done with it,
before you set it to Nothing.

Six of one, half dozen of another as far as reading the registry for that
value. What are you most comfortable with? The only caution is if someone is
running A-V with one of those script stoppers it might prevent the script
access from working.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Rich007" wrote in message
...
Hi Ken, thank you so much for responding.
I tried your suggested extra line of code before creating the MailItem,
but
it made no difference. So I tried gradually commenting out lines of code
until Outlook does quit. It appears to be the line:
Set olInspector = olMail.GetInspector
that is causing the issue. If I don't call that line Outlook quits as
ordered. If I do include that line, Outlook stays in the TaskManager.
Any
ideas?

Thanks also for providing the registry address. I have never used VBA to
interogate the registry. Would you recommend I use the API route as
described he http://support.microsoft.com/default.aspx/kb/145679
...or
go down the scripting route as described he
http://vba-corner.livejournal.com/3054.html ?
(these are the first two results I've found in Google).

Thanks again.
Cheers
Rich