Re: Strange ODBC behavior.

Paul Lambert wrote:
> Paul Lambert wrote:
>> I had a server have a power outage on one of my PostgreSQL servers
>> yesterday and am having a strange ODBC issue now - not sure if they
>> are related occurances though.
>>
>> I have a table called billing_code and one called models in my
>> database. If I connect via psql to the database with my standard db
>> user I can see both of these tables as well as the data contained
>> within.
>>
>> If I attempt to link these tables from MS Access, the billing_code
>> one returns "The Microsoft Jet database engine could not find the
>> object 'public.billing_code'. Make sure the object exists and that
>> you spell its name and the path name correctly" - this error despite
>> the fact that I had to physically select the table from a list it
>> presented me when I went into the linked table manager.
>>
>> If I link the models table, it links fine, but when I attempt to open
>> it, I just get #Deleted in every column of every row for about 54,000
>> rows (the total number in the table)
>>
>> The same problem happens with some of the other tables in the
>> database - some will get the first problem, some will get the second
>> problem, and some will link and load data without issue.
>>
>> I was running odbc driver 8.02.02, I've upgraded to 8.02.04 - just in
>> case there was a problem with the driver getting corrupted but the
>> problem persists.
>>
>> Can anyone offer any thoughts or suggestions on what the problem
>> might be?
>>
>> Thanks in advance,
>> Paul.
>>
>
> I've done a full pg_dump, deleted the database and tablespaces,
> recreated everything, restored the data and the same behavior is being
> exhibited - at least as far as returning #Deleted in some of the tables.
>
> Users with an Access database that already has the table linked don't
> have a problem accessing the data, but those adding a new link to the
> table do.
>
> Any thoughts on this or is it more of an access issue?
1) Could you post here CREATE script for one of the tables with problem
you descrived?  #delete message appears when something happens to the
primary keys.
2) What is the version of your MS Access? PostgreSQL? Unicode or ANSI
driver version?
3) Please, have a look on the linked table structure as it's recognised
by MS Access. And post it here.


Andrei.