Re: Problems with Access XP and text primary keys - Mailing list pgsql-odbc

From Ben Trewern
Subject Re: Problems with Access XP and text primary keys
Date
Msg-id csqlsp$1afi$1@news.hub.org
Whole thread Raw
In response to Re: Problems with Access XP and text primary keys  (laurie.burrow@powerconv.alstom.com)
List pgsql-odbc
Sorry I don't think I explained the problem clearly.  The primary key is a
varchar(250) which I think I should be able to use.  It is defined as a
domain.

If you look at the log entries from the previous post, while the app works
correctly the WHERE clause looks like:

WHERE "user_name" = 'btrewern' OR "user_name" =  'chappellj' OR "user_name"
= 'mcwilliamsf' OR ....

Then suddenly, and I can't explain why, it becomes:

WHERE "user_name" = 'b' OR "user_name" = 'c' OR  "user_name" = 'm' OR ..

Just the first letter of the primary key is used.  This then gives the
errors described.

Any Ideas?

BTW Ive changed back to using the

Ben.


<laurie.burrow@powerconv.alstom.com> wrote in message
news:OF1BADDF84.F5CD0F57-ON80256F90.0032A34C-80256F90.0033829C@transport.alstom.com...
> "Ben Trewern" <bendottrewern@mowlem.com> wrote in message
>
>> I've been using Postgres 8.0rc5 with the pgsqlODBC 8.00.00.03 driver and
>> am having some problems.
>>
>> The database works correctly for some time but suddenly and for no reason
>> I can find I get #Deleted in some of the fields. These tables seem to be
>> those which have text primary keys. I've looked at the psqlodbcXXXX.log
>> and it seems that I get:
>
> I believe Access will give this mesage when the primary key of a record
> has
> been  modified. I think the text type is mapped to memo fields which
> Access
> cannot use as a primary key. If  a table does not have a primary key it
> will use the fields of the original record as sort of combined key to
> identify the record. If any field is changed this will then generate the
> message. It may be that if you set the Row Versioning flag in the postgres
> ODBC driver this may resolve the problem.
>
> Laurie
>
> :.________________
> CONFIDENTIALITY : This  e-mail  and  any attachments are confidential and
> may be privileged. If  you are not a named recipient, please notify the
> sender immediately and do not disclose the contents to another person, use
> it for any purpose or store or copy the information in any medium.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>



pgsql-odbc by date:

Previous
From: "Ing. Jhon Carrillo"
Date:
Subject: Schema?
Next
From: Kris Jurka
Date:
Subject: Re: [JDBC] Schema?