DAO Recordset in .Net

[Dave]

'UPGRADE_WARNING: Arrays in structure rs may need to be initialized before
they can be used. Click for more:
'ms-help://MS.VSCC.v80/dv_commoner/local/redirect.htm?keyword="814DF224-76BD
-4BB4-BFFB-EA359CB9FC48"'

Dim rs As DAO.Recordset

How can this be accomplished ? There are dozens of array elements in this
structure.

What to do ?

 

[m.posseth]

Don`t worry about this , sometimes these upgrade advises are a litle bit
hysteric and see problems where they are not


But if i may ask ,,, do you see a good performance benefit in using DAO in
..Net ?

regards


Michel Posseth [MCP]

 

[Dave]

I've been using VB Versions 4, 5, and 6 and DAO for years. The applications
I write don't have performance considerations. I've just spend some time
upgrading some of them and everywhere I had a DAO recordset declared it put
one of those comments.

I've considered converting these applications ADO and then reconverting them
to .Net, but haven't done it.

I'm really trying to figure out how to prepare my applications best before I
convert them.

I've run into problems with the Tag property that are in virtually all the
controls in VB6 and are only in some in .Net. I've not yet figure out how
to deal with that one. The Tag property problem is much more frustrating
that dealing with all these comments.

Man, it's like the architects of VB.NET didn't even know VB6 existed.

Don`t worry about this , sometimes these upgrade advises are a litle bit
hysteric and see problems where they are not


But if i may ask ,,, do you see a good performance benefit in using DAO in
.Net ?

regards


Michel Posseth [MCP]

'UPGRADE_WARNING: Arrays in structure rs may need to be initialized before
they can be used. Click for more:
'ms-help://MS.VSCC.v80/dv_commoner/local/redirect.htm?keyword="814DF224-76BD
-4BB4-BFFB-EA359CB9FC48"'

Dim rs As DAO.Recordset

How can this be accomplished ? There are dozens of array elements in this
structure.

What to do ?

 

[Peter Huang [MSFT]]

Hi Dave,

In .NET we have a new data access library, ADO.NET.
Commonly we suggest use that in .NET application.
Due to all the components, controls is all redesign in .NET, so the upgrade
may not be smooth, and they are not match one by one.
Commonly the upgrade wizard will use proper control even directly using Com
interop to generate a wrap for the VB6 control.
So we need manually do some upgrades.

But as a best practice, it would better to recreate your code in .NET, the
VB6 class which did not concern with legacy control/com dll may be
migration easier than others, because the syntax between vb6 and vb.net is
compatible.

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.