Its a VB app so everything's single threaded. Instancing is a separate
issue - its set to 'multiuse' in VB so that one server executable will
generate multiple instances of the component.
As I said, it works as I require if every client logs in as the same user
but not otherwise.
I've tried using DCOMCnfg to set the launching user to be the same for all
clients but that doesn't work either.
Thanks for replying,
AJ
"CheshireCat" <(E-Mail Removed)0m> wrote in message
news:eO%(E-Mail Removed)...
> Is this a problem with the way the dcom server application was configured
> when it was written? imho I believe a DCOM app can be set up as
> multithreaded, apartment or single instance which changes the way
> single/muliple copies are opened. I've no idea how this works in practice
> but it was a consideration when I wrote activex controls and I thought it
> may have similar effect in dcom.
> Do a google on "dcom thread models"
>
> CC
>
>
|