Jim,

> If I were attacking the problem, I'd make the "mega-database manager" be
> a separate provider and maintain it's own system tables using a local
> Firebird database. I'd snapshot remote table metadata at creation time,
> and re-validate the snapshots from time to time. I would design and
> implement it to be totally transparent the remote protocol and existing
> clients and tools. I'd also do a clean, modern, object oriented
> implementation.

Are you talking about a mega-database-manager as provider in Vulcan
sense? I mean that one would need to create database through that
provider (or register it in the config file), and later use that very
database to execute cross-database queries, while leaving the
possibility to connect to single databases for "local" table access only?

Or do you mean something different?

Roman