Geoff,

Thanks very much for your response.

Problem #1: decompression length

The first 2,300+ files I restored were fine, then FB choked with the
decompression length problem on my last three files. These three
files were suspect to begin with... I don't own v5.6 for any
platform, so I can't test your theory.

I'll probably need to write a batch move to export the data from the
4.2 machine to the FB machine to circumvent this.

Problem #2: reserved words

Yes, GBAK restored the database files as ODS 10 in dialect 1 with no
apparent difficulty, even with the reserved column names.

I looked at the 6.0 docs, which has the same basic procedure I was
attempting using the IB_WISQL DSQL tab. My error was not committing
the creation of the new column before attempting UPDATE ... SET to
populate the column.

Best Regards,

David Montgomery

--- In ib-support@y..., Geoff Worboys <geoff@t...> wrote:
> > What's the best way to rename a column with a reserved word as its
> > name? How do I even write the script commands without FB choking
on
> > the reserved words?
>
> So GBAK allowed you to restore into an ODS10 (firebird database?)
>
> You can write the script commands by putting the names in double
> quotes. You will probably find it worth looking at the IB6 beta
> documentation - which explains some of new few functionality
> available, including the ability to alter various field attributes
> etc.
>
> The firebird website: http://firebird.sourceforge.net/
> (see links to "Documentation" and "Novice's Guide").
>
> In particular the IB6Beta documentation available from:
> http://firebird.sourceforge.net/index.php?op=doc&id=userdoc
>
>
> Did you solve your earlier decompression length problem? If not, I
> was going to suggest a two stage scenario; use IB5.6 to restore and
> then backup, then go to FB and see if that gets you around it. This
> is presuming that one of the experts here does not have a better
> suggestion.
>
>
> --
> Geoff Worboys
> Telesis Computing