Re: DAO VB ODBC "read only problems

Hiroshi and others,

Nope....

Also tried (randomly):
-Disabling KSQO
-Enabling "Unknowns as LongVarChar"
-Enabling Parse Statements
-Enabling Show System Tables
-Switching to 6.3 Protocol

-Tried to get pgadminII running as an independent test but ran into 7.1
dependency problems. Upgrading the system is a task for tomorrow.

-pgaccess works fine.

-Any other "known good" applications that could be used to verify
functionality?

-Any wisdom on verifying the logs?
the only thing I can see the looks a little ominous is where it executes
"select oid from pg_type where typname='lo'"
and it returns 0 rows. I have no idea what this is...

Thanks for all the help,
Wearing out,

Sam

-----Original Message-----
From: Hiroshi Inoue [mailto:Inoue(at)tpf(dot)co(dot)jp]
Sent: Monday, October 29, 2001 10:56 PM
To: Miller, Sam
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: [INTERFACES] DAO VB ODBC "read only problems

"Miller, Sam" wrote:
>
> Hiroshi and others,
>
> I added:
> wrkODBC.DefaultCursorDriver=dbUseODBCCursor
> after the "Set wrkODBC....." line.
>
> Still doesn't work. Any more ideas?
>
> I discovered I am using postgresql-7.0.2-17, could that be the problem?
> (The ODBC driver is at 7.01.0007)

How about unchecking *Text As LongVarChar* ?

regards,
Hiroshi Inoue