I have a VB program that controls Outlook programatically. The program uses
a class (olwrapper) which in turn uses Outlook to send an email. A snippit
of olwrapper follows:


Dim objoutlook As Outlook.Application
Dim objoutlookmsg As MailItem
Dim objinsp as outlook.inspector
Dim mydoc as word.document
Set objoutlook = New Outlook.Application
Set objoutlookmsg = objoutlook.CreateItem(olMailItem)
Set objinsp = objoutlookmsg.GetInspector
If objinsp.IsWordMail = True Then
If objinsp.EditorType = olEditorWord Then
objinsp.Activate 'this was added for outlook
2007
set mydoc = objinsp.wordeditor
mydoc.range.paste 'inserts info from clipboard
end if
end if


This code has worked fine with Office 2003. I had to insert the
inspector.activate event and it has worked fine with outlook 2007, until one
of my customers recently had a problem. The are using MS Office 2007 Basic
Edition, and the .wordeditor property is not getting set. It is always empty.

I did some further testing and was able to determine that the code works
fine with office 2007 standard and small business, but it does not work with
basic edition.

I inadverently discovered that the code will run with basic edition, if I
start outlook before running the code.

Any help or suggestions is greatly appreciated.

In article ,
=?Utf-8?B?ZnJlZWRiaWxs?= wrote:
I inadverently discovered that the code will run with basic edition, if I
start outlook before running the code.

Any help or suggestions is greatly appreciated.

Have your program create the Outlook Object when it starts. I suspect that
you can keep it invisible, or at least, minimized.

--
Hollis Paul
Mukilteo, WA USA

Thanks, however, my program is creating the Outlook object when it starts.
The unique problem I have is that this program runs fine on several
computers. But it fails on a new computer and the only thing I can identfy
as different is that the new computer is running MS Office Basic Edition.
The problematic computer will run the program okay only if I manually start
Outlook before running the program.

"Hollis Paul" wrote:

In article ,
=?Utf-8?B?ZnJlZWRiaWxs?= wrote:
I inadverently discovered that the code will run with basic edition, if I
start outlook before running the code.

Any help or suggestions is greatly appreciated.

Have your program create the Outlook Object when it starts. I suspect that
you can keep it invisible, or at least, minimized.

--
Hollis Paul
Mukilteo, WA USA

In article ,
=?Utf-8?B?ZnJlZWRiaWxs?= wrote:
The problematic computer will run the program okay only if I manually start
Outlook before running the program.

Then the next best thing is to start Outlook, again in minimized form, during
the boot sequence. I don't exactly know how to do that, but if you have a
boot up script, you can use a command line switch. If you are willing to have
it visible, you just need to put a link in the appropriate start-up folder.
Then it is there when you need it.

--
Hollis Paul
Mukilteo, WA USA