VB6 recordset code to VB.Net -

i updating elses old code vb6 windows application vb.net web application. understand old code, not sure how translate .net recordsets.

mystoredprocedure = "sp_writevpayrollcurrent"         mycurrentpast = "'n'"     mystoredprocedure = "sp_obtainsubclassid"        myclassname = "payroll major"        mysubclassname = "new hire"        set rs = tgetreadresultsetwithparms(myclassname, mysubclassname, (mystoredprocedure)) 

also, not sure happen "mystoredprocedure" being declared twice or error?

the tgetreadresultsetwithparms function follows (some cases redacted free space):

dim en rdoenvironment dim cn rdoconnection dim rq rdoquery   rdodefaultcursordriver = rduseserver 'open connection tstdbexecutive database using dsnless connections set en = rdoenvironments(0) set cn = connectionstring stuff here select case mystoredprocedure     'create reusable rdoquery , call sql server stored procedure.     case "sp_obtainclassid"         set rq = cn.createquery("", "{call " & cstdatabasename & ".dbo.sp_obtainclassid(?)}")     case else         set rq = cn.createquery("", "{call " & cstdatabasename & ".dbo." & mystoredprocedure & "(?)}") end select 'set input argument value store procedure. rq(0) = myparm1 'open resultset , pass calling procedure set tgetreadresultsetwithparm = rq.openresultset(rdopenkeyset, rdconcurreadonly) 

the vb6 code using remote data objects. think have read the documentation understand vb6 doing, , rewrite in vb.net using ado.net achieve same functionality. afaik there no handy cheat-sheet shows how rdo compares ado.net, unfortunately. there some ado-ado.net.

alternatively could add reference remote data objects in .net project - can use com objects in .net - , use same code. if there large amount of old code, pragmatic way make task more manageable, although makes code harder understand other programmers used ado.net. it's better rewrite if can afford to.