ASP Program Performance test report (III)

Should adovbs.inc be referenced by including references?
The adovbs.inc provided by Microsoft contains 270 lines of code that define most of the ADO property constants. Our example references only 2 constants from the Adovbs.inc. So in this test (ado__02.asp) We removed the include file references, and set the properties directly using the corresponding values.
Objrs.cursortype = 0 ' adopenforwardonly
Objrs.locktype = 1 ' adlockreadonly

You can see that the page overhead is down by 23%. This value does not affect the extraction and display time of a single record, because the changes here do not affect the recordset operation within the loop. There are a number of ways to resolve adovbs.inc reference problems. We recommend that the Adovbs.inc file be used as a reference, and that it be explained by annotations when set. Keep in mind, as the first part points out, that proper use of annotations has minimal impact on the efficiency of the Code. Another approach is to copy the constants that need to be used from the Adovbs.inc file to the page.
There is also a good way to solve the problem, which is to make all the ADO constants available directly by linking the ADO type library. By adding the following code to the Global.asa file, you can access all the ADO constants directly:
<!--METADATA type= "TypeLib"
file= "C:Program FilesCommon FilesSYSTEMADOmsado15.dll"
Name= "ADODB Type Library"-->
Or:
<!--METADATA type= "TypeLib"
Uuid= "00000205-0000-0010-8000-00AA006D2EA4"
Name= "ADODB Type Library"-->
Therefore, our first rule is:
L avoid including adovbs.inc files, access and use ADO constants in other ways.