From: NTB Technical Support <techsupport@ntb.org.uk>
To: pgsql-interfaces@postgresql.org
Subject: ADO and ODBC
Date: Wed, 4 Jul 2001 18:14:22 +0100
Message-ID: <00b801c104ac$c578d140$2780bcc3@northeast.co.uk> (raw)
We're trying to migrate some Access databases which have a substantial
number of table row- and column names which contain spaces - and then use
them via ADO/ODBC from Microsoft IIS.
The problem seems to be that if we use the ADO interfaces to update the
contents of a recordset retrieved from postgresql, an ODBC parse error is
generated at the point of issuing the RS.UPDATE if the table name and/or ANY
column name in the table contains a space.
I assume that ADO is, behind the scenes, generating an SQL Update for every
column in the row and something (ADO or the postgresql ODBC driver) isn't
correctly quoting/escaping the table and column names that result.
Is there any way to work round this, short of going through several thousand
lines of ASP and changing the name of every table and column that is
referenced??
Tim Dixon
NTB Tech Support
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: techsupport@ntb.org.uk
Subject: Re: ADO and ODBC
In-Reply-To: <00b801c104ac$c578d140$2780bcc3@northeast.co.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox