Re: BEST odbc driver for windows MS Access - Mailing list pgsql-odbc
From | K. Kelly Close |
---|---|
Subject | Re: BEST odbc driver for windows MS Access |
Date | |
Msg-id | 457CF079.7080906@hydrosphere.com Whole thread Raw |
In response to | Re: BEST odbc driver for windows MS Access (Richard Broersma Jr <rabroersma@yahoo.com>) |
Responses |
Re: BEST odbc driver for windows MS Access
Re: BEST odbc driver for windows MS Access |
List | pgsql-odbc |
This is what I'm not actually sure of, but some more research I've done tonight seems to indicate that the method I've used accessing an OLEDB source entirely from within code (which is what I'm trying to do) may be completely adaptable to an ODBC source.And if not, will I have to go thru MSQuery to get to pgsql via ODBC? I hope not...I am not to sure how to answer your question. What functionality does MSQquery give you that you get some other way with OLEDB.
Using SQL Server as an example, I can connect from Excel VBA using code that looks something like this:
oConn.Open "Provider=sqloledb;Data Source=Aron1;Initial Catalog=pubs;User Id=sa;Password=asdasd;"00)
I was hoping I could replace the "sqloledb" provider with the proper reference for the postgresql oledb provider and have a working connection!
I now find that I can theoretically also connect to SQLServer thru ODBC using a connection string in VBa that looks something like:
oConn.Open "Driver={SQL Server};Server=Aron1;Database=pubs;Uid=sa;Pwd=asdasd;"
So again, if I install the PostgreSQL ODBC driver and put it in there in place of {SQL Server}, I should have a working connection I can pass SQL thru from code...right? :-) That's what I'm going for anyway. I am really just looking to do pretty simple querying and writing back to the database with this. If ANYONE out there has any experience with this, from any MS application using VBA, I would appreciate hearing from them...and any references to other message lists are welcome too - thanks for the pointer to the odbcng list, Richard.
~Kelly
And if anyone has thoughts or experience on OLEDB vs. ODBC for connecting to pgsql from Microsoft software, I'd love to hear of them!My opionion of OLEDB for postgresql is that it is broken and certainly not more stable in this case. Even worse, there doesn't seem to be much support for the oledb project as compared with the odbc projects. If you find that a bug keeps you from completing your project, there aren't very many places to turn. from the following link: http://archives.postgresql.org/pgsql-odbc/2006-10/msg00009.php you see that an old version of ODBC was able to handle a load of 600 transactions requests per second. The Command Prompt odbc-ng appears to almost double this throughput, however it breaks when I try to use it. This should be expected since this driver is still released as being under the "public test mode". If you are enterested in using the odbc-ng driver you could use the following mailing list for help: http://lists.commandprompt.com/mailman/listinfo/odbcng Regards, Richard Broersma jr. ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
-- ************************************** Kelly Close Database and GIS Specialist Hydrosphere Resource Consultants, Inc (303) 443-7839 (303) 442-0616 (fax) kkc@hydrosphere.com Visit our web site! http://www.hydrosphere.com
pgsql-odbc by date: