Skip site navigation (1) Skip section navigation (2)

RE: Access 97 - problems with the result set

From: "Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)uk>
To: "'Joseph'" <lters(at)mrtc(dot)com>, "Pgsql-Odbc(at)Postgresql(dot)Org" <pgsql-odbc(at)postgresql(dot)org>
Subject: RE: Access 97 - problems with the result set
Date: 2001-07-23 08:21:56
Message-ID: E2870D8CE1CCD311BAF50008C71EDE8E01F74635@MAIL_EXCHANGE (view raw or flat)
Thread:
Lists: pgsql-odbc
Hello,
	Couldn't you just do select 't' as t ? This seems to work on MS
Access2K. If you are (for whatever reason) actually wanting to execute the
query on the server instead then try a pass-through query (note:
pass-through queries only return snapshot recordsets).
- Stuart

> -----Original Message-----
> From:	Joseph [SMTP:lters(at)mrtc(dot)com]
> Sent:	Saturday, July 21, 2001 12:44 PM
> To:	Pgsql-Odbc(at)Postgresql(dot)Org
> Subject:	RE: Access 97 - problems with the result set
> 
> 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
> and
> 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
> >
> >
> > respectfully,
> > Joseph
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 5: Have you checked our extensive FAQ?
> >
> > http://www.postgresql.org/users-lounge/docs/faq.html
> 

pgsql-odbc by date

Next:From: Vince VielhaberDate: 2001-07-23 09:35:37
Subject: Re: No permission to set nextval of sequence
Previous:From: Henshall, Stuart - WCPDate: 2001-07-23 08:13:26
Subject: RE: Access 2000 and ODBC driver Data changed by another user, Cop y to Clipboard or Drop changes

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group