Are you using floats? If so then it might be trying to refresh based on all
the fields and failing because of floating point precision.
Make sure that all tables have primary keys and try enabling row
versioning. If you enable row versioning you will need this, or something
similar, in the backend:
create function int4eq(xid,int4)
returns bool
as ''
language 'internal';
create operator = (
leftarg=xid,
rightarg=int4,
procedure=int4eq,
commutator='=',
negator='<>',
restrict=eqsel,
join=eqjoinsel
);
Hope this helps,
- Stuart
> -----Original Message-----
> From: Manfred Kraft [SMTP:mkr@alcedis.de]
> Sent: Monday, September 10, 2001 3:55 PM
> To: 'pgsql-odbc@postgresql.org'
> Subject: 'ODBC call failed' a few seconds after Opening the table in
> Access
>
> Hi,
>
> Does anybody else know that strange behaviour: In nearly each database I
> have one or more tables, losing their ODBC-Connection after a specific
> time
> ofter opening. All other tables of the same database are ok.
>
> Deatils: e.g. there is one table I can be sure that some 3 to 10 seconds
> after having opend its datasheet view in Access I get the "ODBC call
> failed" message and the contents of all fileds change to #NAME? (that's in
>
> the german version; I don't know whether it's the same Error-string in the
>
> english one).
>
> My first idea was, that is has to do with altered tables, but that's not
> generally true.
> Dumping and restoring the database doesn't solve the problem, whereas
> recreating it with my own set of create-statements and afterwards
> inserting
> the data does. But that's no praktical solution.
>
> Thanks for helpful hints.
>
> Manfred