Tony,
Wouldn't the 'simple' way I thought of (i.e., using ODBC and Access
combined) do the trick ?
Regards,
Philippe Bertin.
> -----Original Message-----
> From: tony [SMTP:tony@animaproductions.com]
> Sent: dinsdag 14 mei 2002 16:30
> To: joe@jwebmedia.com
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Using COPY
>
> On Tue, 2002-05-14 at 16:15, Joseph Koenig wrote:
> > We're converting a db from Access to PostgreSQL for a client - I need to
> > export all of his data into postgres on Linux - I'm trying to use the
> > COPY command, however, his comment fields have line breaks in them which
> > causes the copy to throw a parse error at that line. I'm sure others
> > have run into this - is there an easy way to avoid this? Thanks,
>
> Welcome to pain! Now when someone asks me to port data, I bill each and
> every hour spent - no more estimates on how much it will cost!!!
>
> I'm sure someone will recommend a perl script to rip them out.
>
> If you aren't a perl guru then run out and find a Mac with BBEdit which
> is the absolute best text editor in the world. A combination of BBEdit
> and OpenOffice will clean up and format any text file and save it to
> many types of text including CSV.
>
> Cheers
>
> Tony Grant
> --
> RedHat Linux on Sony Vaio C1XD/S
> http://www.animaproductions.com/linux2.html
> Macromedia UltraDev with PostgreSQL
> http://www.animaproductions.com/ultra.html
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly