Mutilated1
May 13th, 2004, 12:26 PM
Hello,
Please forgive me if I am asking this question in the wrong place.
My problem is that I've been given a set of classic ASP pages, that we now wish to run as ASP.NET instead. Most of the conversion issues have been worked out except for one.
Many of the classic ASP pages use ADO for their data access, and I would like to continue using it. But everywhere the .aspx page encounters one of the enumerated symbols from the type library, causes a compilation error similar to this:
Compiler Error Message: BC30451: Name 'adCmdStoredProc' is not declared.
Previously, under classic ASP I was using code like the following to define the symbols in the type library:
<!--
METADATA
TYPE="typelib"
FILE="C:\Program Files\Common Files\System\ado\msado15.dll"
-->
However, this doesn't seem to work under ASP.NET anymore. Can anyone tell me how to make this work ?
I know that I could go through the files and replace adCmdStoredProc with 4. etc... for each place that the undefined symbol causes an error, but I'd prefer not to take that route since the maintainability is important.
Anyone know the solution ?
Thanks!
Please forgive me if I am asking this question in the wrong place.
My problem is that I've been given a set of classic ASP pages, that we now wish to run as ASP.NET instead. Most of the conversion issues have been worked out except for one.
Many of the classic ASP pages use ADO for their data access, and I would like to continue using it. But everywhere the .aspx page encounters one of the enumerated symbols from the type library, causes a compilation error similar to this:
Compiler Error Message: BC30451: Name 'adCmdStoredProc' is not declared.
Previously, under classic ASP I was using code like the following to define the symbols in the type library:
<!--
METADATA
TYPE="typelib"
FILE="C:\Program Files\Common Files\System\ado\msado15.dll"
-->
However, this doesn't seem to work under ASP.NET anymore. Can anyone tell me how to make this work ?
I know that I could go through the files and replace adCmdStoredProc with 4. etc... for each place that the undefined symbol causes an error, but I'd prefer not to take that route since the maintainability is important.
Anyone know the solution ?
Thanks!