As Michelle and Steve noted earlier, there are some of us experiencing
this anomaly with MS-Access, PostgresqlODBC + Postgres.
My configuration...
Gentoo Linux 2.4-something...
PostgreSQL 7.4.6
ODBC (8.00.00.04, but have tried many others)
I'm basically having the same problem. It doesn't seem to occur on all
tables. I am turning on query logging on my database tonight and will
report results based on my findings.
./Peter
Peter T. Bense - Teradata Certified Professional
(ptbense@gwm.sc.edu) - 803-777-9476
Database Administrator/Webmaster
Prevention Research Center
University of South Carolina
>>> Steve News <earlysteve@earthlink.net> 2/15/2005 2:32:19 PM
Joost,
I'm going to jump in here. I work with Michelle, but am having trouble
posting to the pg list. When we look at the log files, some times we
see
strange things. I don't have them handy to cut and past here, but for
example, I can request all rows from a table (no "where" clause"). Then
in
the log, I may see three queries. The first is correct. Then, there are
two
that on their own have added a where clause that restricts the data by
saying record_id = {some random big integer having nothing to do with
nothing}. Then the table opens with every dell filled with #delete#.
--steve backman
>>> Michelle Murrain <tech@murrain.net> 2/15/2005 1:13:39 PM >>>
We have a MS Access 2000 database connecting to psgl 7.4.5 database
over the Internet using ODBC 7.03.02.00 drivers. The connection works
sometimes and then fails sporadically and unpredictably. When it fails,
it could be just opening a table or it could be in a bound form. When
it fails, we sometimes get an ODBC connection error. Sometimes, the
table opens up with each cell filled with #delete#. I'm looking for
some general troubleshooting guidelines.