No such thing as small code. It can be kind of lengthy code.
Firstly though we need to know what your environment would be, and I mean specifics because it changes with every version...
We need to know:
RDO, ADODB or ODBC access to the database?
Microsoft's or Oracle's drivers?
Version of Visual Basic and Oracle.
Version of MDAC and the DAO libraries on your machine.
Version of the Jet Libraries on your machine.
Intranetwork or Internetwork?
Connecting will require specific code on both sides so it just isn't a Visual Basic issue but you have to write your stored procedures in a specific way as well. You do know PL/SQL correct?
If you’re still watching this thread, I can shed some light on the subject. Although Wayne is correct that VB to database interaction can get very involved, basic operations are quite easy: reads can be done with a few statements; writes are just as easy if your not concerned with transactions processing (making sure ALL of a group of database changes take place, or NONE of them happen). The hardest part is determining the connection from VB to Oracle. However VB has a nice utility that will set up ODBC or a native driver -- the proces is twisted, but easy.
Posting Permissions
Bookmarks