2.02 b1

First of all, I prefer old way of reverse enginner: triggers were
created just afeter table creation, now they are created at the end of
script.

But with an existing database, running 2.02 reverse enginer has
duplicate triggers: after table creation and at the end of script.

BTW, why do you add constraints via ALTER TABLE in auto reverse
enginer scripts? Formerly where created on CREATE TABLE

I've send you a copy of this script.

Tiago Ameller
tiago put_an-a-_in_a_circle sistemasc.net
Sistema, S.C.

> BTW, why do you add constraints via ALTER TABLE in auto reverse
> enginer scripts? Formerly where created on CREATE TABLE

Because of the thread in the suggestions group entitled, "reverse
engineer => install script".

(http://www.elevatesoft.com/newsgrp?action=openmsg&group=10&msg=2651&pag
e=1)

--
David Cornelius
CorneliusConcepts.com

David,

>Because of the thread in the suggestions group entitled, "reverse
>engineer => install script".

Ok, I see the motivation. But you'll need to rearange generated script
in most cases due a procedure is calling another procedure declared
last. I think is more readable to see all related to a table near it,
but, it's not a great matter.

I guess "reverse enginering" needs some improvements ...


Tiago Ameller
tiago put_an-a-_in_a_circle sistemasc.net
Sistema, S.C.

Tiago,

<< But with an existing database, running 2.02 reverse enginer has duplicate
triggers: after table creation and at the end of script. >>

Yep, you are correct.  I'll make sure this is corrected.

--
Tim Young
Elevate Software
www.elevatesoft.com