X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id CBF3E8BA2DC
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Fri, 18 Feb 2005 14:55:42 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 31136-05
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Fri, 18 Feb 2005 14:55:36 +0000 (GMT)
Received: from vms040.mailsrvcs.net (unknown [206.46.252.40])
	by svr1.postgresql.org (Postfix) with ESMTP id C8A178BA256
	for <pgsql-sql@postgresql.org>; Fri, 18 Feb 2005 14:55:38 +0000 (GMT)
Received: from jfradkin ([66.15.127.235])
	by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix
	0.04 (built Dec 24 2004)) with ESMTPA id
	<0IC40033U44QFZ00@vms040.mailsrvcs.net> for
	pgsql-sql@postgresql.org; Fri, 18 Feb 2005 08:55:39 -0600 (CST)
Date: Fri, 18 Feb 2005 09:59:26 -0500
From: "Joel Fradkin" <jfradkin@wazagua.com>
Subject: =?iso-8859-1?Q?trrouble_inserting_stuff_like_=E9?=
To: <pgsql-sql@postgresql.org>
Message-id: <000001c515ca$7146a740$797ba8c0@jfradkin>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=3.192 tagged_above=0 required=5 tests=AWL,
	FORGED_RCVD_HELO, MSGID_DOLLARS
X-Spam-Level: ***
X-Archive-Number: 200502/207
X-Sequence-Number: 20318

I wrote a program to read my database (from MSSQL) and write it to =
Postgres.
It appeared to work great the first time I ran it, but the database was
SQL_ASCII (It defaulted to this when I created it from the command line =
on
the linux box using createdb.

When I tried to restore it I used PGAdmin on my XP machine which created =
a
Unicode database.
I was unable to restore the SQL_ASCII to the Unicode, so I re-ran my =
import
on a Unicode database.
Now I get all kinds of errors from the .net program (which I have write =
out
the actual SQL on each error).
When I cut and paste the SQL into PGADMIN it runs ok, so it only gives =
an
error using .net ODBC.

Any one have any clues for me to follow?

Here is an example of a SQL line that did not run in .net.

insert into
tblSuspectedActivity(ClientNum,ID,Value,IsDeleted,PresentationID)
values('FREN',4,'Paiement =E0=20
account',False,2)

Joel Fradkin
=A0