P
Pablo Montilla
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi, sorry for the long post, but I don't know how to fix this
problem.
I'm using an Access 2000 mdb as front-end for a postgres database
that has tables with case sensitive names. That means that the
queries should be written with quotes in the identifiers.
I'm using the Access ODBC driver and ColdFusion to issue the queries.
When I do an update to a table, the Access ODBC driver tries first to
pass the query as I've written it (without quotes), and when it
fails, it issues a select and then reissues the query with the quotes
(I think that the first select is to get the correct structure so it
can rewrite the query).
So far so good. The trouble starts when I try to do updates inside a
transaction. As access issues the first (bad) query, the transaction
is aborted and I'm stuck.
Now the question: is there an odbc parameter or something that I can
use so the first query (the bad query) doesn't get to the server?
Many thanks, and again, sorry for the long post.
Pablo Montilla
- --
For many are called, but few are chosen.
-- New Testament
-- Matthew xxii, 14
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
iQA/AwUBQVruJL6KEogX0AkqEQIcbACglw/IO4GMhR8xAJnJcfKShWBpUhAAnRNL
SvXtop6YrI2vx0+DCx0N/MTY
=ORPu
-----END PGP SIGNATURE-----
Hash: SHA1
Hi, sorry for the long post, but I don't know how to fix this
problem.
I'm using an Access 2000 mdb as front-end for a postgres database
that has tables with case sensitive names. That means that the
queries should be written with quotes in the identifiers.
I'm using the Access ODBC driver and ColdFusion to issue the queries.
When I do an update to a table, the Access ODBC driver tries first to
pass the query as I've written it (without quotes), and when it
fails, it issues a select and then reissues the query with the quotes
(I think that the first select is to get the correct structure so it
can rewrite the query).
So far so good. The trouble starts when I try to do updates inside a
transaction. As access issues the first (bad) query, the transaction
is aborted and I'm stuck.
Now the question: is there an odbc parameter or something that I can
use so the first query (the bad query) doesn't get to the server?
Many thanks, and again, sorry for the long post.
Pablo Montilla
- --
For many are called, but few are chosen.
-- New Testament
-- Matthew xxii, 14
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
iQA/AwUBQVruJL6KEogX0AkqEQIcbACglw/IO4GMhR8xAJnJcfKShWBpUhAAnRNL
SvXtop6YrI2vx0+DCx0N/MTY
=ORPu
-----END PGP SIGNATURE-----