Received: from s20.highertech.net (root@s20.highertech.net [209.54.120.20]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA90711; Fri, 28 May 1999 11:53:45 -0400 (EDT) (envelope-from jt-kirkpatrick@mpsllc.com) Received: from kirkpatrickjt (whiteoak-34.highertech.net [209.140.56.34] (may be forged)) by s20.highertech.net (8.8.6/8.8.6) with SMTP id LAA15182; Fri, 28 May 1999 11:53:34 -0400 Received: by localhost with Microsoft MAPI; Fri, 28 May 1999 11:55:07 -0400 Message-ID: <01BEA900.EE6149C0.jt-kirkpatrick@mpsllc.com> From: JT Kirkpatrick To: "'pgsql-interfaces@hub.org'" , "'pgsql-admin@hub.org'" Subject: odbc driver failing. . . Date: Fri, 28 May 1999 11:55:06 -0400 Organization: MPS, LLC X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 Encoding: 16 TEXT hi all. i have written in about illegal page faults when i try to add records to a particular table -- editing it seems fine. well, i have narrowed down another "weird" problem with the same table. i reported that when i open it directly in datasheet view, the odbc driver fails every time. this is not my largest table at all -- this one is 14M and over 45k records -- my largest is 23M and over 90k records. i can open every other table up in datasheet view (msaccess97 by the way) except the 14M one. here is the log file after i opened a few other tables and then finally the one that bombs -- does anyone have any ideas about what is going wrong?? a few suspects -- the table has a field defined as varchar(300) and another varchar(550) -- i have the odbc driver set to cache 1000 (at least in this log file -- it was 100 and still bombed!), maxvarchar=550, maxlongvarchar=15000. but editing the table a record at a time -- or even pulling up a subset of records from the table works fine. . . thanks for any suggestions! jt