Hi Dmitry,

Thanks for the reply. I will create this as a DLL. Creating this as an ATL
DLL will solve all my issues.

Thanks!



"Dmitry Streblechenko" wrote:

You can create your form server in a dll rather than an exe.
The CFG file will still be the same; it is just under the covers Outlook
will be creating your form as an in-proc COM object. Of course your dll must
conform to all the usual COM rules, but ATL should be able to handle that
with no effort on your part.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"Tom at GSD" wrote in message
...
Hi,

I have created a custom form ATL local server that interfaces with Outlook
and my message store for one of our customers. The form server supplies a
custom form for the open message form of my private message class. I have
run
into a unique problem that obviously requires marshalling. Since it is a
local ATL server I am unable to get string properties from my IMessage
interface within my message store. I get the standard COM errors for
unable
to retrieve the data. I have a couple questions that I am hoping someone
may
shed some light on.

1. Can we create the Form Server as an inproc server and do away with the
local server? If so how do I denote that within the CFG file? I have read
a
couple old articles that say that this is not possible.
2. Does anybody have any sample marshalling code necessary for the MAPI
Message store?

Thanks,
Tom -