Running ADO (VB6) along side ADO.NET

[ragstta]

Hi All,

We have a three tier windows app:
- data layer
- Business layer
- Windows Forms

We've half upgraded to .net from vb6
the only thing left to upgrade is the datalayer. They datalayer still uses VB6 ADO.

For a smooth transition can we have both the OLD ADO VB6 and ADO.net libraries worlk along side each other:
- Could they use the same connection Object?
- Will using both mean I have to have two active connections?

Your probably thinking why do we want to use both?
- Its mission critical code so the old stuff must still use ADO VB6
- all new classes will use the ado.net objects

thanks in advance

[Campion]

Is it safe to assume that the code for this "mission critical" application no longer exists, hence sticking with the VB6 program? Otherwise, I see no reason why you couldn't upgrade it to .NET (aside from the translation required.)

[ragstta]

All our business classes have reference to adodb.recordset
we dont want to change those

but instead have new classes for new stuff that use ado.net

so thats why im asking Running ADO (VB6) along side ADO.NET in the same app

[Campion]

I see.

As long as the server is set up to accept multiple connections at the same time (which is its default behavior,) you'll be fine. This is especially usefull when you need to run a program and also run the management studio.