dcsimg
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: Web
Expertise: All
Jul 29, 1999

WEBINAR:

On-Demand

Building the Right Environment to Support AI, Machine Learning and Deep Learning


Avoid ADO Errors by Including ADOVBS.INC

The IntelliSense feature of Visual InterDev is very handy, but it may induce you to add bugs to your code. For example, when you are using a recordset object's Open method, IntelliSense prompts with this tool tip:

 
Open(Source, ActiveConnection, [CursorType], [LockType], [Options])

When you get to the CursorType parameter, IntelliSense pops up the available choices such as AdOpenDynamic and AdOpenKeyset. That's where the bug sneaks in. Even though you think you've added a constant such as AdOpenDynamic, you haven't actually done so in ASP. Your "constants" will all resolve to zero--probably not what you wanted. The trick is to always include ADOVBS.INC in your database scripts such as:

 
<%
<!--#INCLUDE FILE="adovbs.inc"-->
%>

The alternative is to use the actual values for ActiveX Data Objects (ADO) parameters instead of the more meaningful constant names.

Ken Cox
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date