Answering my own question, partly...
Turns out access seems upset at least some of the time if
there are no REAL fields returned from the database.
So if we have a table foo with a field f1
we query it this way - SELECT 't' as t from foo
there is no error on postgresql but access first runs the query as is then
tries 'SELECT * FROM SELECT 't' as t from foo' which causes an error on
server, and therefore the error on access.
Any thoughts about how to fix this other that doing adding a REAL field so
it dosen't fail
as - 'SELECT 't' as t,OID from foo' (which works fine).
> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org]On Behalf Of Joseph
> Sent: Saturday, July 21, 2001 7:19 AM
> To: Pgsql-Odbc(at)Postgresql(dot)Org
> Subject: [ODBC] Access 97 - problems with the result set
> I am running access queries and it seems that it thinks certain
> queries were
> unsuccessful when in fact they were successful...!
> Is there something special that access expects to get back which
> indicates a
> successful query?
> Of course access appends the horrid select * from to the front of
> the query
> and then postgres promptly gives and error.
> Access then reports an error. Even though the original query executed fine
> on the server.
> Postgres 7.1.2
> odbc 7.01.0006
> win2k is the client
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
In response to
pgsql-odbc by date
|Next:||From: Hiroshi Inoue||Date: 2001-07-21 16:10:29|
|Subject: RE: ODBC performance with ADO|
|Previous:||From: Joseph||Date: 2001-07-21 11:19:25|
|Subject: Access 97 - problems with the result set|