Re: IIS Postgres ASP ADO - Problem

James,

The odbc is not working well for me (I can connect but get intermittent
issues of the IIS server locking up in regards to connectivity).
My understanding is the snapshot version is the best odbc out at this time.

Also can you connect via pgadmin (IE have the hba and config files set to
allow external connections)?

My conection is not using dsn, but I did get dsn to work in testing.
My dsnless string is

Session("StringConn") =
"DRIVER={PostgreSQL};DATABASE=wazagua;SERVER=192.168.123.121;PORT=5432;UID=p
ostgres;PWD=;ReadOnly=0;Protocol=6.4;FakeOidIndex=0;ShowOidColumn=0;RowVersi
oning=0;ShowSystemTables=0;ConnSettings=;Fetch=100;Socket=4096;UnknownSizes=
0;MaxVarcharSize=254;MaxLongVarcharSize=8190;Debug=0;CommLog=0;Optimizer=1;K
sqo=1;UseDeclareFetch=0;TextAsLongVarchar=1;UnknownsAsLongVarchar=0;BoolsAsC
har=1;Parse=0;CancelAsFreeStmt=0;ExtraSysTablePrefixes=dd_;LFConversion=1;Up
datableCursors=1;DisallowPremature=0;TrueIsMinus1=0;BI=0;ByteaAsLongVarBinar
y=0;UseServerSidePrepare=0"

My test using dsn used
Session("StringConn") ="DSN=postgresql;" & _
         "UID=postgres;" & _
         "PWD=;" & _
         "Database=wazuni;"

asp code to use connection is :
  dim Arec, Acmd, SQL ,AConn
  set Arec = server.CreateObject("ADODB.Recordset")
  Set AConn = Server.CreateObject("ADODB.CONNECTION")
  set Acmd = server.CreateObject("ADODB.Command")
  AConn.ConnectionTimeOut=30
  AConn.commandtimeout=30
  AConn.Open Session("StringConn")

For .net I use the npgsql .net objects.

Hope this helps you.

Joel Fradkin




-----Original Message-----
From: James Dornan [mailto:james@catch22.com]
Sent: Sunday, July 31, 2005 4:44 PM
To: jfradkin@wazagua.com
Subject: IIS Postgres ASP ADO - Problem


  I noticed more than a few post from you about trying to get Postgres
working with ODBC.
I'm hoping that maybe you would share some of that information. I am
running IIS under
windos 2003 server, and the latest(8.0.3) Postgres server on the same
machine. I cannot
connect no matter what I do. I have tried everything.

  The funny part is that I'm not new to ODBC, or windows. I've worked
with windows all
the time, but just can't figure this one out. I've tried using a
connection string, a DSN,
reinstalling, IIS, Postgres, ODBC drivers, MDAC, Jet, and so on. I still
have the same problem.
The odbc drive and it's dependant DDLs are in the path. The permisions
are wide open
(for testing this specific problem).

  Is there any insight you could shed on the dark world of windows and
ODBC, where feed-
back is rare.

  Thanks for any help you can provide.

-- James