serious problems with BOOL and Access - Mailing list pgsql-interfaces

From Markus Wagner
Subject serious problems with BOOL and Access
Date
Msg-id 0202141342410C.21071@magnus
Whole thread Raw
Responses Re: serious problems with BOOL and Access
List pgsql-interfaces
Hi,

we're in serious trouble with an application using BOOLs. We have boolean 
attributes in a pg table, being represented as checkboxes in Access. Changing 
these controls results in an error message "another user has changed the 
data", or something like that.

We tried nearly everything. The mailing list archives gave hints to the pg 
ODBC driver, the "bools as char" flag and so on. We tried with and without 
this flag. Then, without it, the problem seemed to be solved. But we found 
that now the data must have been changed several times in different records, 
before the problem reappears.

Our current settings are "bools as char" off, "text as longvarchar" off. The 
bools are normal BOOL attributes of size 1, as reported by pgaccess. We also 
tried to change the table properties for the fields in Access, "display as 
checkbox" and so on. We drag the fields from the field list into the form. 
But also changing the ODBC-connected tables directly results in the same 
error.

Isn't there a unique solution to that? Why are bools that critical?

Thank you very much,

Markus


pgsql-interfaces by date:

Previous
From: BELLON Michel
Date:
Subject: Re: Using libpq with Borland C++ Builder
Next
From: Holger Marzen
Date:
Subject: Re: [GENERAL] pgaccess failed, used to work