Mike,

>> If you had "a lot" of .DBCs each with "a lot" of tables, it could get painful >to open that page.
>
>I've tested performance with up to 2000 tables. At 1280, it gets painfully slow, something like five minutes. At around 1792, the DBC designer never opens.

Just for my information, how is performance when using such a big DBC in a real time application ??

I guess we don't really need the database designer as when hitting this kind of problems we could also use commands like ALTER TABLE, INDEX ON, PACK DATABASE etc...

Walter,