Received: from auth1.interpath.net (auth1.interpath.net [199.72.1.129]) by hub.org (8.8.8/8.7.5) with ESMTP id HAA28545 for ; Thu, 13 Aug 1998 07:58:34 -0400 (EDT) Received: from BethLechem.Yehudah.lee.k12.nc.us (sanford0-089.dyn.interpath.net [207.59.120.89]) by auth1.interpath.net (8.8.5/v1.0) with SMTP id HAA29190; Thu, 13 Aug 1998 07:58:30 -0400 (EDT) Message-ID: <010801bdc6b1$e40cd840$01cc0cac@Yehudah.lee.k12.nc.us> From: "James Oden" To: "Bryan Brunton" Cc: Subject: Re: [INTERFACES] '\' and varchar data type problem w/ MS Access and ODBC driver Date: Thu, 13 Aug 1998 07:46:51 -0400 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.0518.4 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0518.4 > >The backslash character '\' seems to cause problems when using the >varchar >data type. MS Access will refuse to update a varchar field if 3 >backslashes >have been inserted. If you want litterally three backslashes you may need to massage the data to add an extra one before each one, so your three back slashes become six back slashes. I am just guessing on this, but in postgreSQL's implementation of SQL (and this may be just a SQL thing) the \ is used as an escape sequence, much like it is in C. Someone else on the list earlier had a problem recreating his databases from a dump because it did have \'s in it....james