Rather than merely fix the exceptions you are seeing, I would alter the code
to use the ADO.NET model rather than use Interop to ADO. The enums should be
available through interop, but it is far less efficient than refactoring to
the new model.
---
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
"Vic Spainhower" wrote:
> Hello,
>
> OK - I'm trying to make the big jump from vb6 to vb.net. I took one of my
> vb6 programs and ran it through the converter and I'm getting some ADO
> errors that indicate a reference is required. I have a reference set to the
> 2.8 library.
>
> Here's some examples of the errors:
>
> Reference required to assembly 'ADODB' containing the type
> 'ADODB.CursorLocationEnum'. Add one to your project.
> Reference required to assembly 'ADODB' containing the type
> 'ADODB.LockTypeEnum'. Add one to your project.
> Reference required to assembly 'ADODB' containing the type
> 'ADODB.CommandTypeEnum'. Add one to your project.
>
> What reference do I need to add? I put together a test program with an ado
> recordset, referencing the 2.8 library and it worked fine. Under references
> on the form it is properly showing 2.8 as being referenced. Of course the
> form design won't come up because the error line is inside the generated
> code "Initialize Component"!
>
>
> TIA,
>
>
> Vic
>
>
>
|
Similar Threads
