This content has been marked as final. Show 3 replies
Well, unless you were using OO4O in .net applications there's no way to port them to ODP.net without starting over. OO4O was meant for stuff like VB, I'm not sure it was ever a good idea to use it in .net.
Now, what I'd agree with is that they don't seem to have provided good documentation on porting away from OO4O to anything. Considering that it's discontinued, that would be useful information. ODBC and ADO are probably the best options for something like a VB 6 application, but we haven't looked into it very much yet.
I figured as much. I'm also porting the app from VB6 to .Net.
In that case, there's no particularly good way to port it. ADO.net is so different from OO4O that you're best bet is just to read some tutorials on how to use ADO.net and ODP.net, and just start rewriting the database connectivity layer.