Skip site navigation (1) Skip section navigation (2)

Re: Problems with Access XP and text primary keys

From: "Ben Trewern" <bendottrewern(at)mowlem(dot)com>
To: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Problems with Access XP and text primary keys
Date: 2005-01-21 10:37:35
Message-ID: csqlsp$1afi$1@news.hub.org (view raw or flat)
Thread:
Lists: 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(dot)burrow(at)powerconv(dot)alstom(dot)com> wrote in message 
news:OF1BADDF84(dot)F5CD0F57-ON80256F90(dot)0032A34C-80256F90(dot)0033829C(at)transport(dot)alstom(dot)com(dot)(dot)(dot)
> "Ben Trewern" <bendottrewern(at)mowlem(dot)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
> 



In response to

pgsql-odbc by date

Next:From: kj subbuDate: 2005-01-21 14:21:58
Subject: ksqo is not valid option name
Previous:From: laurie.burrowDate: 2005-01-21 09:20:42
Subject: Re: Problems with Access XP and text primary keys

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group