On 20/08/2013 4:08 AM, Tim Young [Elevate Software] wrote:

>
> So, I'm guessing that you want to *force* the use of UNI as the
> collation and ignore the collation from the incoming DBISAM 3.x tables
> ?  If so, then I'll have to think about this one since I can't change
> the default behavior without breaking existing applications.
>

My understanding of the default behaviour of the migrator seems to be
wrong. Now I understand that what I expected to happen can not occur
without breaking existing applications.

The solution is now outlined in the thread 'How to generate a script for
altering objects in a database?". With Roy Lambert's help there is now a
script to change a collation. So far that script seems to work for me.

So, if I am not mistaken, I can automate the running of that script
after the automated migration is run.

Regards,
  Peter Evans

Tim


>Thanks. They thought she had 2, and when they got in there they found 6
>(!!).

Ouch

><< 2. I like the sound of a Bat Mitzvah did you take photo's >>
>
>Unfortunately, taking pictures in the temple was a no-no (at least for us
>guests). She had a professional photographer taking photos, though.

So no pictures of bats then

Roy

Peter,

<< So, if I am not mistaken, I can automate the running of that script after
the automated migration is run. >>

Yes, that is correct.

Tim Young
Elevate Software
www.elevatesoft.com