pcPirate,
Whichever way you go, you will have to use COM interop to do this. If
you can completely isolate all of the data access into a VB6 set of
components, then you probably should do that, as it will cut down on the
interop you will have to do with .NET if you made the calls to the RDO
components through COM interop.
Basically, create your COM component (ActiveX dll project in VB6). Once
you have the dev done on that, you can set a reference to the component by
selecting "add reference" when right clicking on the references folder in
your project. It will show up in the COM tab.
When distributing your application, make sure that you distribute the
interop dll that is created, as well as your VB6 dll, and RDO, as all of
those will need to be on the machine that you are deploying to.
One thing, since you have the option of containing all of your data
access in a single component, I don't understand why you need to use RDO.
What is the requirement that says you have to use that?
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- nick(dot)paldino=at=exisconsulting<dot>com
"pcPirate" <ph****@hotmail.com> wrote in message
news:ug**************@TK2MSFTNGP10.phx.gbl...
Hi,
I'm currently writing an application using C#. However, to access and
update a database, I must only use rdo (due to a certain reason). I heard I can
use the VB6 to make the function of accessing and updating the database and
then, compile it into dll. After that, using the C#, adding the reference
of the dll, I would be able to access or update the database.
Q1) Is this true?
Q2) If so, how do I do that? Can anybody share some codes about this?
Thanks in advance
pcPirate