Ann W. Harrison wrote:

>>I believe you could resolve this problem with FBCopy tool:
>>
>>1. Do a metadata-only backup of your database
>>
>>gbak -b -m -v old.fdb meta.fbk
>>
>>2. Restore it to some new.fdb
>>
>>gbak -c -v meta.fbk new.fdb
>>
>>3. Use FBCopy with D option to list tables:
>>
> Unfortunately, the order of backup is not defined by the query in
> backup.epp, so it defaults to the order in which the table definitions
> were stored, not the order in which the data is stored.

I know. I was suggesting the idea that he doesn't do the regular
backup/restore at all, only do a metadata backup/restore and then pump
the data instead of backing it up. I can even exapand this idea:

I propose that he use gbak/FBCopy to split the backup in two pieces.
As he wrote, he can't separate the data in database. But he didn't say
that he can't separate the data in backup. I'll try to explain better:

- backup&restore metadata to 2 to-be-backuped databases
- copy old "payment history" tables to 1st
- copy new "payment history" tables to 2nd
- back up each one. Well, it is enough to create backup for old data
once, and leave it be. That's why I didn't mention it before.

This way he can leave the old never-changing payment history tables in
one backup file, and only selectively backup the "live" data.

Of course, I might have misunderstood the original problem. If I did,
then just forget about this.

--
Milan Babuskov
http://fbexport.sourceforge.net