In a windows 2000 server with D3NT and IIS and a web application is
better D3ODBCSV (ODBC Library) than D3OLESRV (OLE Server Library)?

thanks,

Marcos.

ODBC is cleaner, OleSrv is faster.

When an ODBC connection breaks for some reason (eg, user X's off the
application), eventually the ODBC driver will drop the process.

When an OleSrv connection breaks, you have to reboot the machine to get them
back.

Personally, I push people towards MV.NET for web applications. It's clean,
it's fast and it doesn't pollute the pool with dead processes.


Mark Brown


<alonvega (AT) hotmail (DOT) com> wrote

ODBC is clean unless you let MS Query or some other tool auto-guess at the
table relationships. I dunno how many times our Linux box has been scrubbed
into the ground by a run-away ODBC request that had some kind of circular
link setup. It tends to happen when you add nested tables to a primary table
and the tool automatically tries to join the tables together. I mentioned
several times to support about setting a memory limit on the ODBC service
for Linux and Windows to prevent Death-By-Circular-Join. Windows has
physical memory limits too, so a circular link between 2 or 3 tables would
probably kill a Windows server.

Glen

"Mark Brown" <mbrown (AT) drexelmgt (DOT) com> wrote

I want to use the D3CLODBC client library. I don't want to use SQL
tables

Thanks,

Marcos

Glen B ha escrito: