Fernando,

This is now fixed, and a fix will be included in 2.24 B3 due out shortly.

The problem was introduced when the new built-in reverse-engineering functionality was added to EDB.  The migrator was simply not setting the INFORMATION COLLATE clause in the right place before grabbing the SQL from the system information tables in the source system:

http://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=SET_INFORMATION_COLLATE

Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

many thanks.

We will be waiting for that release, until then, as Fernando suggested, we have played changing collation from source ANSI database to ESP and the process works, but still throws an exception:

ElevateDB Error #401 The collation ANSI does not exist in the configuration EDBConfig

Thanks.

Miquel,

<<ElevateDB Error #401 The collation ANSI does not exist in the configuration EDBConfig>>

Perhaps because you still have some ANSI reference somewhere in the source database...

--
Fernando Dias
[Team Elevate]

Roy,

With or without documentation I'm close to madness, it's been 36C to 38C in Lisbon, my brain is about to melt!

--
Fernando Dias

Fernando


That's one of the reasons we moved up to the Scottish Highlands - we had a summer where I had aircon and ended up putting baking foil over the windows to reflect the sun.

Don't get much sun now - just turning rusty with the rain.

Roy Lambert