ODBC Connection

rhett7660

Still Learning....
Local time
Today, 01:35
Joined
Aug 25, 2005
Messages
371
Hello...

Question, do you need one for your database and if so why? I have read what they are but I haven't found really why you would need it?

Don't know if this is the right place to post this question but wanted to get some input on this.

Thanks
R~
 
If I am understanding this correctly does it speed up the process within the database? IE you don't have to go through the ado>>ole db... with the odbc it just has the one step?

Or am I missing what it is saying.

Also what is the prevailing census that you need to make sure your db has an odbc? Or does it do it automatically? I have setup via the odbc connection in windows...

Just wondering if I am doing something that should be done or it doesn't matter if it is done....

Thanks
R~
 
Bob has basically told you about these. You wouldonly use them if you want to access data held in a different(non Access) db. ie MySQL,ORacle, Foxpro etc.
 
You're building complexity where there is none. Once again, the only reason you have an ODBC connection is for connecting to a data source that is not Access. For example, I go through an ODBC connection at work to connect to a DB2 database. This doesn't make it faster -- it just makes it possible.

Think of it this way. I want data from a DB2 database. I am using Access, which is not compatible with DB2. The ODBC Driver is the translator between the two. Therefore, from Access I send a query. The ODBC Driver takes that query and translates it into something DB2 can understand. DB2 does its thing and is ready to send the results back to Access. DB2 sends its results to the ODBC Driver, which translates it into something Access understands. And all is good with the world.

Without the ODBC Driver as a "middleman", you can't connect to other data sources that Access doesn't inherently understand. That's all it is. There are SQL Server Drivers, FoxPro Drivers, DBASE Driver, etc. All of them do roughly the same thing for their associated data sources. Unless you're using something that Access doesn't inherently understand, there's no need for an ODBC Driver or any other "middleman" as it were.
 

Users who are viewing this thread

Back
Top Bottom