> A> IIS is a threading application service. It wants to load the
> ISAPI module
> A> once and run it multiple times on different threads. This does not lend
> A> itself to using the embedded version which is a "one-man-team"
> so to speak.
> A> Even if you play around with when your module actually
> connects to your db
> A> and disconnects, you will certainly suffer concurrency
> lockouts from the
> A> server.
>
> did you try it?
> What are your suggestions/assumptions based on?
>
> Ciao
> --
> Nando Dessena
> mailto:nandod@...

Suggestions: Use the full server. Some one else here tried it the other day
and couldn't work out why it won't work.
ISAPI has always wanted a TCP connection string - it won't work with a local
connection string... why? because it needs to make trheaded connections. Try
it, you'll find out how quickly it locks up.
I can only imagine that people are tempted to use the embedded server
because it means they can deploy on a hosted server without need for there
provider to set them up with FB. Great idea but it won't work.
Alan