This is just a guess, but could the problem have to do with those huge varchar fields
in your
tables? I had problems using varchar over 255 characters from Windoze ODBC clients
quite a long
time ago (I was using PostgreSQL 6.0, and later 6.2, with quite an early version of
PostODBC that
still had a lot of bugs). The tables would only cause problems with the Windoze ODBC
clients--the
Web-based application and Linux shell operations were fine and the database integrity
was not
affected.
I ended up solving the problem some time later. First I upgraded the ODBC driver (it
was changing
almost daily at the time it seemed), then I changed the large varchar fields to the
'text' type.
When I linked the tables the 'text' type in PostgreSQL translated to the MS Access
'memo' type.
That seemed to remedy my problem. Although I don't believe the 'text' data type is
standard SQL,
it seemed to work better for large fields and I had better luck using it with
PostgreSQL's
built-in string functions.
I hope this helps...
Mark.
JT Kirkpatrick wrote:
> i got no response on the interfaces list -- maybe someone here has
> experienced this too??
>
> (msaccess97 / win98, 6.40.0005 odbc driver, postgres 6.4.2, linux mandrake
> 5.3) i wrote earlier about getting illegal page faults every time i CLOSE a
> certain form (it lets me use it just fine!) that is used to ADD RECORDS
>
[...]
> of access! i figure that is because of the size of the table. i have
> cache set to 100, maxvarchar = 550, maxlongvarchar=15000. in the table i
> have one field varchar(300) and another varchar(550). a few "checks"
> (state char(2) not null check (state<>' ')). -- ok that's all i know that
> would be suspicious. but the edit forms work fine. i also have several
> other add-new-record forms set up in the same way that use other tables --
> they work fine. any ideas???
[...]
>
>
> jt
