Actually the "AspCompat" attribute causes the thread to execute in a STA
rather than a MTA, and somewhere in the code of the page you create the
class which calls the COM obj, still in the same thread, so you must use the
"AspCompat" attribute.
It may be a security issue then, specially if the COM obj is an out of
process exe.
To test it, switch anonymous access off to the virtual directory and use
impersonation,
http://msdn.microsoft.com/library/de...ersonation.asp
"Bruce Whitehouse" <sk*******@yahoo.co.uk> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Yes I have.
It's set to true!
this only sets the compatability for the aspx page. I've a separate class
that calls the COM+ object.
Regards,
Bruce