Re: VB6 to VS.Net 2003 DLL change

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I respect your opinion, however, in this case it's fairly large VB6
dll - - - there are approximately 100 lines that do this kind of thing - -
I just need to find out how to replace the existing code with working DotNet
code - - that will go a long way to getting this thing working - -
Yes, there will be more cleanup - - but, by far, the majority is merely the
changing of lines like this.

AND - I don't have the time to sit down and re-write someone else's DLL
myself - - this will definitely be the quickest solution.

If someone has the actual answer to this question, I would appreciate it
greatly.

"Norman Yuan" <NotReal@xxxxxxxxxxx> wrote in message
news:umTMgH8FGHA.1192@xxxxxxxxxxxxxxxxxxxxxxx
> This may not answer your question, but, since it is database application
> with ADO, it simply no point to convert it into .NET, if you still use ADO
> in .NET. In .NET app, you should use ADO.NET, which is so different from
> ADO, that you just cannot convert to it from an ADO app. You need to
> rewrite the code of data access part. It is waste of time to do the
> conversion, IMO.
>
> "David Wier" <dwier@xxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:O4DCUX7FGHA.3700@xxxxxxxxxxxxxxxxxxxxxxx
>> I'm trying to convert a VB6 DLL (that someone else wrote) - many lines
>> are parameters that need converting that have 'System.DBNull.Value' in
>> the original - - the report says this is an erroneous use of the
>> Null/Isnull . Here's the code:
>> If BillCust > 0 Then
>> Call colParams.Add(objDB.CreateADOParm("@BillCust",
>> ADODB.DataTypeEnum.adInteger, ADODB.ParameterDirectionEnum.adParamInput,
>> BillCust))
>> Else
>> 'Error Message --------> 'UPGRADE_WARNING: Use of Null/IsNull() detected.
>> Click for more:
>> 'ms-help://MS.VSCC.2003/commoner/redir/redirect.htm?keyword="vbup1049"'
>> Call colParams.Add(objDB.CreateADOParm("@BillCust",
>> ADODB.DataTypeEnum.adInteger, ADODB.ParameterDirectionEnum.adParamInput,
>> System.DBNull.Value))
>> End If
>>
>> How can I change the 'Else' section so it will work in DotNet?
>>
>>
>
>


.

Relevant Pages

  • Re: VB6 to VS.Net 2003 DLL change
    ... with ADO, it simply no point to convert it into .NET, if you still use ADO ... In .NET app, you should use ADO.NET, which is so different from ... It is waste of time to do the conversion, ... > ADODB.ParameterDirectionEnum.adParamInput, BillCust)) ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: Conversion from BDE to ADO
    ... I've noticed no performance problems with ADO and MSSQL. ... conversion). ... > I am currently experimenting with converting a quite large app from BDE to ...
    (borland.public.delphi.database.ado)
  • Re: Access Development Freelance
    ... >stress the importance of disambiguating all of the reference uses. ... A97 mdb that had a reference to ADO below DAO is pretty ... ADO reference instead of moving the DAO ref up the list. ... he had just let Access do the conversion, ...
    (comp.databases.ms-access)
  • Re: vb5 versus vb2008
    ... my advice is to learn the VB5 application's functions. ... DAO is not supported and has not been for some time. ... COM-based ADO is different from ADO.NET. ... not ease the conversion in any useful way. ...
    (microsoft.public.vb.database)
  • Re: Sql server to xml string with encoding
    ... between text handling in ASP and ADO vs ASP.NET and ADO.NET is that whereas ... completely ignorant of any encodings, and doesn't do textual conversion, the ... Even if this binary treatment of text was A Bad Thing with ASP ...
    (microsoft.public.dotnet.framework.adonet)