Thanks to each of you who responded...
I did figure out the problem.
The NT4 box was using MS Access 2000, after seeing a few other post on
"[INTERFACES] Access 2000 and empty fields"... I decided that upgrading MS
Access 2000 to Service Pack1, the MS JET to Spk5, and the MS MDAC to 2.6
were all great ideas.
I did all of them, and additionally turned on the OID field in the ODBC
driver, and have since used the OID as the unique field identifier... and
viola! Life is good... It seems that my actual troubles were the following:
In my meanderings I found a Q-Article on the Microsoft website that said
something like "text" is converted to "memo" for MS Access, and there was a
bug about using a "memo" field as a unique ID field. Although I can not for
the life of me find that article again on the MS site.
As for the query itself, I never even ran it... I only "linked" to the
tables via ODBC from MS Access 2000, and the "text" field that I selected to
be the unique identifier, had all it's data destroyed.
-Michael Miyabara-McCaskey
> -----Original Message-----
> From: pgsql-interfaces-owner@postgresql.org
> [mailto:pgsql-interfaces-owner@postgresql.org]On Behalf Of
> Tibor Laszlo
> Sent: Tuesday, November 21, 2000 1:56 AM
> To: mykarz@miyabara.com
> Cc: pgsql-interfaces@postgresql.org
> Subject: Re: [INTERFACES] ODBC Windows driver corrupts data?
>
>
> > I am having a rather strange, highly annoying problem. Any
> help would be
> > appreciated.
> >
> > I am running PostgreSQL 7.0.2 on Linux 2.2.17, and I have
> the ODBC (windows)
> > driver running on WinNT 4.0 spk6.
> >
> > The problem itself seems to be that if I try and do
> anything with a "text"
> > field from the Windows machine, it deletes ALL the data
> from that field, in
> > the entire table.
> >
> > The only change I did to the ODBC setup was turned the
> default "Read Only"
> > off.
> >
> > Has anyone else experienced this?
>
> Sorry for the late post. What kind of software makes your
> UPDATEs? Or do
> them you? And can you get the ODBC log to view what UPDATE sent to the
> backend caused this? (You can turn on the driver log vith the
> CommLog check box
> on the Advanced Options (Driver) dialog. I think its better
> than the Win ODBC
> DriverManager's tracing.) We make C++Builder apps with
> ODBCExpress and we always
> watch the log files... I think your UPDEATE's WHERE clause
> was wrong. But
> let's see the log...
>
> Regards, Tibor
>
> --
> Tibor Laszlo
> ltibor@mail.tiszanet.hu
>