Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SamC
White Water Yakist
3467 Posts |
 Posted - 2003-08-26 : 13:58:55
|
| There's an article at[url]http://www.interspace.net/aspcdo.html[/url]That describes including CDO and ADO constants using a technique I haven't seen:<!--METADATA TYPE="typelib" UUID="CD000000-8B95-11D1-82DB-00C04FB1625D" NAME="CDO for Windows Library" --><!--METADATA TYPE="typelib" UUID="00000205-0000-0010-8000-00AA006D2EA4" NAME="ADODB Type Library" --><!--METADATA TYPE="TypeLib" FILE="C:\WINNT\system32\cdosys.dll" --> I've been including ado.inc using <!--#include file="ado.inc" -->Is using one of the approaches above a better solution? Faster maybe?Sam |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-08-26 : 19:13:23
|
It saves you the hassle of having to include the include file  and I think it improves performance when instantiating objects. One downside is that you get all of the type library loaded, when you may not need all of the items. I just created my own short version of the ADO include file that's about 85% smaller than the original. It may or may not matter, but I know it's taking up less memory than the entire type library would. |
 |
|
|
|
|
|
Including ADOSYS and CDOSYS constants