Fredrick,

Vulcan will not make any incompatible changes to the
gbak format. The additional facilities you suggest sound
very good. There are slight problems with an XML/text
representation of floating point data - but that's probably
not terribly important. As for coding in Pascal, well,
I guess if none of it goes into gbak itself, that doesn't
matter much. But you ought to try C++, it's not that bad.

The major tricky part about gbak is that objects have to
be created in a specific order. Views after the tables they
reference, etc. That's all in the logic of the backup module,
and not documented. (Do you see a pattern here?) As you
get into selective restore and the like, you should be aware
of the order of dependencies...

Best regards,


Ann