Well sure, the JDBC drivers should be better, yes. With ODBC (since CFMX 6), you're going through an ODBC-JDBC bridge, so if you can skip that, it will be better. It's really only there for backward compatibility for those who for some reason have no JDBC alternative they can use. And Adobe even included a JDBC driver for MS Access, so that one need not use ODBC even for that.
I'll note that this sort of stuff is discussed in the CF docs, in the "Admin and Config Manual". No offense intended in mentioning that. It's just that many never even notice that it exists.
No offense taken.
I appreciate any and all info you provide.
I haven't looked over the detailed documentation in years.
It seems like the positions I am in, are more the "jump in and go" methodology. ;-)
And my spare time I try not to look at the CF manuals unless I have to!
They're all JDBC drivers. CF can only use JDBC drivers. Most are "pure" Type 4 JDBC drivers, which means that they only include Java code. Others are "impure" - they include something else: ODBC or some other native code. Generally, Type 4 JDBC drivers will provide better performance, as they involve fewer levels of indirection. The only drivers that aren't Type 4 JDBC drivers are the two Access drivers and the "ODBC Socket" driver, if I recall correctly.
Dave Watts, CTO, Fig Leaf Software
Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on
GSA Schedule, and provides the highest caliber vendor-authorized
instruction at our training centers, online, or onsite.
Read this before you post:
(As it is not the easiest thing to find .. ) there is a nice breakdown of the driver types here
Well, that's a page within the Admin and Config manual that I pointed to earlier in the thread. But sure, it's not a bad idea to point to the specific page. I'm just reasserting the value of that CF manual (and the others).
>> I'm just reasserting the value of that CF manual (and the others)
Absolutely. But having fallen into the "did not know it existed for years ..." category, I have since found that particular breakdown very useful. So I guess I figured a preview/affirmation of the jewels in the documentation you described could not hurt
Well, perform the following seem to work for me.
For Microsoft Access DB.
1. Load %windir%\sysWOW64\odbcad32.exe
2. Create a new Microsoft Access Datasource and give it a name (you'll need it name later).
3. Go to CF Admin ->Datasource page.
4. Create a new Microsoft Access Datasource (using the datasource name from step 2).
5. Save changes and ignore the error message.
6. Verify connection and you should not see that stupid architecture mismatch error message.
7. Notice CF will still create a datasource in the 64 bits odbcad32.exe
I was looking for a JDBC driver for one of my project but find out the right one in each once there were some problems while connecting to my database then i got one JDBC driver here http://www.datadirect.com/products/jdbc/index.html and it worked for me.You can also go there and download for free trial.Just try it.
You can go for more drivers her for downloads ODBC driver
Europe, Middle East and Africa