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