Pavel Cisar wrote

>You actually don't need external data sources as having name spaces to
>logically divide data and "selectable" backup (ability to tell gbak what
>you want to backup, at least to backup just one name space instead whole
>db) should give you the same result.

Are you talking theoretically, or does something like this already exist?

If we're talking theoretically, it would be more useful for us if they were actually two
physically separate files. We like to be able to transfer customers' "configuration data" to our
office to help our support staff understand the customers' situations. If that part of the data
was in its own fdb file, we could just pull it with PC Anywhere or a VPN connection. But running
a gbak to create a smaller file to transfer would probably require some intervention by the
customer. Would it be possible to modify FB to be able to specify which fdb file each table goes
into, and split a database that way?