Should I update adovbs.inc ?

[kybbe]

Hi!

I always reference adovbs.inc in my "database pages" (SQL Server, stored procedures etc). I have never updated this file, and receive no errors from using it. Should I update to a later version, if so for what reason as I apparently do not need any extra constants?

could my use of this older version (I think it´s from 1997)
have any impact on the webserver? The webserver is IIS 5
and before that I used the same adovbs.inc on IIS 4

Grateful for comments on this

Thanks in advance
/Anders

 

[clarkin]

As to your question: no, I don't think they have changed the ADO constants (the file is just a big long list of variables that are hardcoded into VB, but not in VBscript).
So your adovbs.inc file should still be fine.

However, you really shouldn't use it at all
Have a read of this:

http://www.aspfaq.com/show.asp?id=2112

I use the actual integer numbers instead of the variable names - just open adovbs.inc in notepad and print it off. There's your reference

Posting code? Wrap it with code tags: [ignore]

[/ignore][code]CodeHere

[ignore][/code][/ignore].

 

[palbano]

Personally i always look to upgrade as the primary option then i proceed to prove it wrong. If i can't prove it flawed i then upgrade. Of course the proving involves testing.

The reason i have a bias towards upgrading is to accommodate future application enhancements. If you find you are forced to upgrade to implement you application feature enhancement, the project then involves changing and testing twice as many things so it is twice the complexity.

Of course the risk of changes when not required is also something to consider. It’s almost like they are equal unless you are certain one way or the other, we will never change the app vs. we always have to change the app.


-pete