Time it, the first time ADO runs generally it'll take longer than com, but after that it's generally faster due to caching in classic asp giving preference to ado over custom objects. (I use ASPTime.dll for this but most dev's have a millisecond timer component to use).
For .net it shouldn't matter much...everything's pre-compiled, and, the doc's I've read so far seem to discourage using MTS when ADO can do the same thing under .net. tom mallard seattle -----Original Message----- From: Roji Thomas [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 3:26 AM To: ActiveServerPages Subject: COM vs ASP code for data access Using a COM over ASP code for data access gives performance gain on an IIS 5.0, MTS and SQL server platform? we are having a debate on it. Like to know what u masters think and also point me to some URL with info abt it TIA Roji Thomas --- You are currently subscribed to activeserverpages as: [EMAIL PROTECTED] To unsubscribe send a blank email to %%email.unsub%% --- You are currently subscribed to activeserverpages as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED]
