ADO.NET in VB6

[vul]

May ADO.NET be used in VB6 ?
I'm not asking about using it in DLL created in VB.NET or C# and then DLL is
used in VB6. I'm asking about direct using.
I need some of ADO.NET features, which are not available in a traditional
ADO, and I need them in VB6 project.

Thank you
Al

 

[Shawn Wildermuth (C# MVP)]

Hello vul,

Unfortunately no. You could wrap ADO.NET in a COM wrapper, but that would
be a nightmare. WHat features? Perhaps there is an ADO way of doing what
you need...


Thanks,
Shawn Wildermuth
Speaker, Author and C# MVP
http://adoguy.com

 

[vul]

I have 10 ADO recordsets in VB6 program. All of them should be edited on
Pocket PC, then edited data should be returned into SQL Server.
It looks like pretty easy task via :
1. create ADO.Net dataset, containing all those data,
2. save it as a single XML file,
3. sending to Pocket PC user,
4. User makes changes via VB 2005 program and saves them
5. Send updated XML back
6. Populate ado.net dataset by opening XML
7. Save data back to SQL

With a standard ADO I do not see such an easy solution. There are some other
problems with creating DLL in VB 2005 working with VB 6, but I already
almost did that part. Maybe I'll meet some other problems

Al

 

[Cor Ligthert [MVP]]

Al,

As you ask the question than the answer is simple "No"

Cor

 

[Steven Nagy]

I'm not asking about using it in DLL created in VB.NET or C# and then DLL is
used in VB6.

Actually, yes you are. ADO.NET is a DLL called System.Data.dll and a
few other dlls.

As Cor says, the answer is NO.

However, if you want to use ADO.NET, then you would need the .NET
framework on the PC, in which case, why not do it all in .NET?

Otherwise, just stick to your plan from before, except use VB6 to parse
the returned XML and reconstruct it. Or write your own EXE in .NET that
accepts the XML, and returns an ADO recordset. Then continue on with
your VB6 app.

 

[Marina Levit [MVP]]

I think it would be easier from VB6 to just manipulate the XML document.

 

[Earl]

If you are using SQL Server for the backend, why make the end run around
merge replication? Let the server do all the heavy lifting. It takes about a
page of code to set up merge on the PocketPC.