SQL 6.5 Named-pipes Transport threads issue

When using Named-pipes Transport to access an MSSQL 6.5 server from Delphi
under Windows 95/98, the MSSQL driver is creating one (maybe two)  threads
per connection. Under NT, no threads are needed. This causes an unacceptable
number of threads when a large number of queries are active.

Switching to TCP transport stops the threads from being created... But I
have read that only Named-pipe connections are correctly timed-out...

P.S. Sorry about the multi-postings - I ran out of disk space, and Outlook
kept sending the same messages (It needs free space to delete the e-mail
from my outbox!!)

--- Jeremy