Alan,

> I'm not sure you are talking about something which is not there already.

If

> you mean db design, reverse engineer, update model and then update db from
> updated model, the ibexpert does do this from the designer interface.

That I know.

> If you
> mean something else then I've missed your point.

Yes, I mean something else. Here is a fictive example :

Suppose you have your very own way to implement audit trails and hence can't
rely on existing logging tools. Say you want one tracking table per
monitored table (just a supposition). Probably, a good deal of the tracking
table's structure maps the monitored table's one.
To avoid double work, you could write a script/template that builds a DDL
SQL script from the main model to generate those tracking tables. When you
modify a monitored table, the tracking tables are maintained for you.

I hope it's clearer now.

--
Jerome