I'm reimporting a DB exported from ASA5.5 into ASA8.02.
It would appear that lines containing strings with o-acute (ASCII 243) throw
the system somewhat - it buggers up the field delimiters within the line.
I can preprocess the data to eliminate this problem, but I'd like to know
what other characters exhibit this property? - is it defined anywhere in the
docs?

Clarification:
The SQL that fails is

LOAD TABLE "DBA"."Epostcard" FROM '/home/db/dmcc/unload/b4' FORMAT
'ASCII' QUOTES ON ESCAPES ON STRIP OFF CHECK CONSTRAINTS OFF
DELIMITED BY ',';

Where b4 might contain

'20000422080122','jjcanton (AT) uol (DOT) com.ar','José
Cantón',2,'jjc (AT) uol (DOT) com.ar,j_canton (AT) uol (DOT) com.ar','My new contact
numbers','Just thought I''d tell you I''ve got new Voice and Fax
numbers','Y','07050-681-000','07050-681-000','E',2000/apr/22
20:06:47.845000,'Connections'

And the DBserver complains that Connections isn't a timestamp

Change of question!

How can I get the dbunload utility from SQLAny5.5 to output in the escaped
format (eg "\xf3")

Alex Lake wrote:
I would fire up the 5.x database on an 8.x engine and use the 8.x unload
utility.

Hope this helps,
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/

indicating a corrupt db file).
What I've now done is to go through each data file, substituting any
characters > ASCII(127) with their \escaped equivalents. This seems to have
worked well.