I want to rebuild an ASA6 database with a specific CodePage (CP850) to
SQL Anywhere 10.0.1 CP 1252.
Workaround wit -ct switch for dbengine doesn't works with version 10.
Data unloaded are ok only problem is that dbunload produce reload.sql
with "ENCODING 'cp850'" option for LOAD statement. If I manually
remove this options are data in new DB also ok. How can I tell to
dbunload to produce reload script without this option?

thanks

Mike

Mike,

Why do you not want to search and replace cp850 by cp1252 in the reload
file?

Frank

On Tue, 27 Nov 2007 13:13:38 +0100, Mike <mike (AT) marekedv (DOT) de> wrote:

On Nov 27, 2:04 pm, "Frank Ploessel"
<fpl... (AT) d_e (DOT) i_m_s_h_e_a_l_t_h.c_o_m> wrote:
I want to upgrade from version 6 to 10, and 10 does not support older
database versions. Version 10 has not CP 850.

Mike,

Actually, ASA10 supports codepage 850 ("dbinit -le" in a command line
outputs the supported code pages, and cp850 is still contained).
But ASA10 always translates the database data to and from the codepage of
the operating system when you access it.
From your post, I assume you used a cp850 database on Western European/US
Windows (CP1252) without translation. This means that the ASCII codes used
by Windows were used as ASCII codes in the old database with codepage 850.
This has worked for most characters apart from slight sorting and
comparison issues.
And what you now have to do in order to have a clean database for future
(and for migration to ASA10, you have to unload the data anyway) is
unloading the data without translation, and reloading them without
translation again.
The easiest way to do that is as I had suggested: Generate the reload.sql
script, and before executing it, just in an editor replace the old
codepage with the new one in the LOAD table statements (a global search
and replace should do).

Frank


On Tue, 27 Nov 2007 16:09:38 +0100, Mike <mike (AT) marekedv (DOT) de> wrote: