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
NTB Tech Support
pgsql-interfaces by date
|Next:||From: Hiroshi Inoue||Date: 2001-07-04 23:15:34|
|Subject: Re: non-us datestyle|
|Previous:||From: Oscar Serrano||Date: 2001-07-04 16:43:36|
|Subject: RE: non-us datestyle |