Access 2002 linked table behavior
am 12.12.2008 20:01:58 von ssufficoolThis is a multi-part message in MIME format.
--===============0357604019==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C95C8C.1B9EFBB0"
This is a multi-part message in MIME format.
------_=_NextPart_001_01C95C8C.1B9EFBB0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
I am debugging a certain application *cough* ArcGIS *cough* using Access
2002 linked tables and PostgreSQL. I am able to get the application to
recognize and work with SQL 2005 linked tables, but it won't with
PostgreSQL linked tables.
=20
I have traced all commands going to PG using the pgodbc debug logs and
all the queries are fine. So, now I am left with the ODBC / DAO layers.
I think this has something to do with MSSQL IMAGE versus the PG bytea
type since when it get to handling the bytea blobs, this is where it
seems to crash. I have verified at the DAO layer that all data types and
table/field attributes match between MSSQL and PGSQL linked tables.
=20
If I trick the app by allowing initial connect to the SQL linked tables
and then swap the link for the PG table all goes just fine and I can see
the queries passed to PG and drawn on the application screen, but I cant
get the app to do the initial connect to the PG linked table.
=20
Is there any extra debug information I can get from the ODBC driver to
see where the failure is?
=20
Stanley Sufficool
Systems Analyst
San Bernardino County
909-387-2102
=20
P Please consider the environment before printing this e-mail or its
attachment(s)
=20
------_=_NextPart_001_01C95C8C.1B9EFBB0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
charset=3Dus-ascii">
debugging a=20
certain application *cough* ArcGIS *cough* using Access 2002 linked =
tables and=20
PostgreSQL. I am able to get the application to recognize and work with =
SQL 2005=20
linked tables, but it won't with PostgreSQL linked =
tables.
traced all=20
commands going to PG using the pgodbc debug logs and all the queries are =
fine.=20
So, now I am left with the ODBC / DAO layers. I think this has something =
to do=20
with MSSQL IMAGE versus the PG bytea type since when it get to handling =
the=20
bytea blobs, this is where it seems to crash. I have verified at =
the DAO=20
layer that all data types and table/field attributes match between MSSQL =
and=20
PGSQL linked tables.
trick the app=20
by allowing initial connect to the SQL linked tables and then swap the =
link for=20
the PG table all goes just fine and I can see the queries passed to PG =
and drawn=20
on the application screen, but I cant get the app to do the initial =
connect=20
to the PG linked table.
there any extra=20
debug information I can get from the ODBC driver to see where the =
failure=20
is? size=3D2>
Sufficool
Analyst
County
Webdings">P style=3D"FONT-SIZE: 18pt; COLOR: green; FONT-FAMILY: 'Courier =
New'"> style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">=20
style=3D"FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: =
'Arial','sans-serif'">Please=20
consider the environment before printing this e-mail or its=20
attachment(s)
------_=_NextPart_001_01C95C8C.1B9EFBB0--
--===============0357604019==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-user s
--===============0357604019==--