There's a reference to adovbs.inc in the code. What is it, why doesn't it work without it, and where can I get it?
When writing database related code in ASP, you're really using
ADO (ActiveX Data Objects) which is Microsoft's set of components
which provide programmatic database access. ADO defines a lot of
different constants which you can use to make code more readable
and easier to follow and debug. In order to use these constants
in VBScript you need to define them. This is where adovbs.inc
comes in.
The adovbs.inc file contains a list of the ADO constants and
their numerical equivilents and when included in your ASP code,
it defines them as constants so you have access to them in your
code. There are a lot of these constants and most of our code
is relatively simple database code so it only uses a few of
them, but some you might recognize are adOpenStatic,
adLockReadOnly, adCmdText, etc...
The reason the code doesn't work when you forget to include
the file is that the constants the code uses aren't defined.
The result is that incorrect values get passed to ADO and it
doesn't know what to do with them.
In terms of getting a copy, you probably already have one!
Do a search on your system for adovbs.inc and you'll almost
certainly find the copy that was installed with ADO. If you
can't find one you can get a copy of the one I'm currently using
for the samples from here.
In your sample for getting a database count you say that you can use the following: SELECT COUNT(field_name) FROM table_name; I have done this and am having trouble accessing the value.
By default this syntax doesn't give you a known name for the field which contains the count so the easiest way to get it is to use the ordinal value like this:
rsCount.Fields(0).Value
If you want to use named fields you need to tell the data source what you want to call it in the SQL query like this:
SELECT COUNT(field_name) As some_name FROM table_name;
If you do that then you can use this syntax as well as the one above:
Please note: This form is only for submitting questions about the sample for us to consider including in the FAQ. If we feel the question merits inclusion, we will include it along with a reply. We will not respond to your email individually.
