Received: from londrina.psmi.intranet (server.col.psi.br [200.203.189.130]) by hub.org (8.9.3/8.9.3) with SMTP id HAA85321 for ; Tue, 26 Oct 1999 07:15:49 -0400 (EDT) (envelope-from juarez@correio.com) Received: (qmail 9004 invoked from network); 26 Oct 1999 11:23:46 -0000 Received: from unknown (HELO foz) (172.16.1.39) by 172.16.1.1 with SMTP; 26 Oct 1999 11:23:46 -0000 Message-ID: <000901bf1fa3$80f2f680$270110ac@psmi.intranet> Reply-To: "Juarez Rudsatz" From: "Juarez Rudsatz" To: References: <199910260300.XAA06890@hub.org> Subject: Re: pgsql-sql-digest V1 #393 Date: Tue, 26 Oct 1999 09:16:08 -0200 Organization: =?iso-8859-1?Q?Psmi_inform=E1tica?= MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 > Date: Mon, 25 Oct 1999 16:49:07 -0700 (Pacific Daylight Time) > From: Andrew Perrin - Demography > Subject: Access and field sizes > > Greetings- > > I'm in the process of porting a database from Access to postgres, and have > run into a snag. The snag involves boolean fields using checkboxes in > Access forms; they always return a useless Microsoftish error: > > The field is too small to accept the amount of data you attempted to add. > Try inserting or pasting less data. > > This happens when a checkbox is clicked to set a boolean value to True, > but not when it is clicked to set the value back to False. > > Does anyone have any experience or idea where to go with this? > > Thanks- > Andy Perrin > > - --------------------------------------------------------------------- > Andrew J. Perrin - aperrin@demog.berkeley.edu - NT/Unix Admin/Support > Department of Demography - University of California at Berkeley > 2232 Piedmont Avenue #2120 - Berkeley, California, 94720-2120 USA > http://demog.berkeley.edu/~aperrin --------------------------SEIU1199 > Recently I has a little problem with boolean fields in ODBC access to postgres. The type of field was char. In the ODBC driver configuration there are a advanced option : "Bool as char". Take a look. Juarez Rudsatz