Re: linking access using ODBC driver with geometric data

From: "Jeff Eckermann" <jeff_eckermann(at)yahoo(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: linking access using ODBC driver with geometric data
Date: 2005-08-07 23:45:22
Message-ID: dd66ek$1o49$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Jeff D. Hamann" <jeff(dot)hamann(at)forestinformatics(dot)com> wrote in message
news:TcudneZxRZ6qhG3fRVn-gQ(at)scnresearch(dot)com(dot)(dot)(dot)
> Sorry for the seemingly novice posting, but I could find a solution for
> this on the web so far...
>
> I've been developing a database using postgresql (and loving it) and have
> started running into problems with attempting to update records using the
> ODBC connection. The tables that contain geometric fields are causing the
> problems. Whenever I try to update a record that contains a geometric
> field (any field) I get the following error message:
>
> ODBC -- update on a linked table 'public_locations' failed.
> ERROR: invalid input syntax for type point: "(100),(100)" (#7)
>
> When I attempt to update the record without the quotes, as if typing
> 100,100 in the point field, I get the error:
>
> "record has been changed... blah, blah, blah..."

You mean the old "record has been changed by another user"? If so, try
setting the "row versioning" driver option to true.

>
> Is there some trick to being able to use the geometric data types if
> you're going to interface with Access using the ODBC driver?
>
> Jeff.
>
> ---
> Jeff D. Hamann
> Forest Informatics, Inc.
> PO Box 1421
> Corvallis, Oregon USA 97339-1421
> 541-754-1428
> jeff(dot)hamann(at)forestinformatics(dot)com
> www.forestinformatics.com
>
>

Browse pgsql-general by date

  From Date Subject
Next Message Christopher Browne 2005-08-08 03:48:33 Re: postgresql Secure Mode
Previous Message Marc G. Fournier 2005-08-07 21:29:35 Re: tsearch2: very slow queries