Multi-Database Connection Control to Connect to different databases different ways

Multi-Database Control - Version 3.1.0 - 12/05/2006

In this updated zip file you will find two projects for using the control. One is with a form RSdbControl.ocx and the other is Window-Less (No Forms, RSdbControl.dll). This will show you how to use the control both ways.

Connect and use different vendor databases without the headache of knowing the basic differences for each vendors database. Just register and place the database control onto your form and use the example project of how to connect as a guide and you will be connected to the database of your choice. This control supports ODBC, OLE DB and JET connections. The following databases are supported: If your database is not in the list then it will probably still work with an ODBC connection.

Code:

---

Access 3.51                  JET  OLEDB  ODBC 
Access 4.0                    JET  OLEDB  ODBC 
Oracle                                    OLEDB  ODBC 
Oracle Ms Driver                          OLEDB  ODBC 
IBM UDB                            OLEDB  ODBC 
Pervasive SQL                      OLEDB  ODBC 
SQLServer 2000                      OLEDB  ODBC 
MySQL                              OLEDB  ODBC 
SQLServer Express 2005              OLEDB  ODBC

---

The zip file contains two VB Project (source code) as an example of how to use this control. You must register the RSdbControl.ocx or RSdbControl.dll (depending on which you are using).

(for RSdbControl.ocx)

In VB go to Project->Components then select the RS Multi Database Connection. Add the control to the form and you are now ready to use the program.

or

(for rsdbControl.dll - WindowLess)

In VB go to Project->References then select the RS Multi Database Connection. use the line Set SomeVar as RSDatabase in your module and you are now ready to use the program.


You should register the ocx/dll first before opening the program for the first time. If you first load the program first, VB may complain that there is a problem with the form. This will be because the OCX is not registered and will need to be deleted from the form and re-added. Of course after registering it. If you are not sure how to register the file... We have included a batch file that can register it for you. The name of the file is REGIT.BAT and if you run it the OCX will be registered.

There is a databases Access 2000 (Jet 4.0) named Access2000.mdb. This will allow you to see the ease that you can get an app connected without knowing many of the details. All the supported databases can connect just as easily. There is a generic ODBC connection, but no specific date/time routines are supported for this connection_

Supported Features

Specific date/time formatting routines for the supported databases. Never worry about if your date is in the correct
format. The control handles the formatting.

Can generate three different type log files. Debug, Transaction and SQL trace. Which can help you debug your
application. All of which are under user control. Log files are located in a folder named \dblogs\ in your .LogPath
folder have the file name format of:

Database Type_Connection Type_yyyymmdd.trn (err, trn, dbg or log)

Transaction tracking tracks your begin and end transaction calls (when used with controls begin/end transaction calls).
So that un-committed transactions are automatically rolled back (even nested ones). Even if you forget to rollback
when closing your program the control will not. Keeps your database from corrupting (especially MS Access databases).

this wont work with .NET 2003 right?

Never tried it. Does .Net 2003 support calling vb6 dll's. If so then it will.

I forgot this was even here. I just updated the control to the latest version.