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

RE: A problem with the nextval('') function

From: "Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)uk>
To: "'Ray Daigle'" <rdaigle(at)click2net(dot)com>, pgsql-odbc(at)postgresql(dot)org
Subject: RE: A problem with the nextval('') function
Date: 2001-07-30 08:34:37
Message-ID: E2870D8CE1CCD311BAF50008C71EDE8E01F7464B@MAIL_EXCHANGE (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
	Sounds like you need to use a pass through query (as they're called
in MS Access)
- Stuart

> -----Original Message-----
> From:	Ray Daigle [SMTP:rdaigle(at)click2net(dot)com]
> Sent:	Monday, August 27, 2001 6:57 PM
> To:	pgsql-odbc(at)postgresql(dot)org
> Subject:	A problem with the nextval('') function
> Hi,
> I've been writing a VB application that uses ODBC driver to
> access a PostgresSQL database.  Everything works OK until I try using the
> 'nextval' function.  When I try to execute SELECT nextval('userid') ,
> either from my application or from the Visual Data Manager tool, I get an
> error that states: "The SELECT statment includes a reserved word or
> argumnet name that is misspelled or missing, or the punctuation is
> incorrect.  Number 3141".
> The same query works fine on my database if I'm just using the standard
> UNIX PostgreSQL client, it's only when I try to execute it through ODBC
> that I get a problem.
> Does anyone know if the version of the psqlodbc drivers support
> the nextval function in a SELECT query?
> Thanks,
> Ray Daigle
> Technical Analyst
> Click2Net Inc.
> Tel: (905) 271 3550 ext. 222
> Fax: (905) 271 3650
> rdaigle(at)click2net(dot)com

pgsql-odbc by date

Next:From: Jussi JaaskelainenDate: 2001-07-30 09:34:25
Subject: odbc and bit-field
Previous:From: Dave PageDate: 2001-07-30 07:19:38
Subject: RE: [ODBC] Visual Basic and PostgreSQL ODBC

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