Subject | Re: [firebird-support] Registry/Error Codes/Converion to 2 |
---|---|
Author | Helen Borrie |
Post date | 2007-01-24T14:46:01Z |
At 10:15 PM 24/01/2007, you wrote:
directory of your Firebird installation. It will install the
Registry keys and then all you need to do is export them.
the documentation area was created by me from the v.1.5.2 messages
database. It's not a straightforward query at all, in fact the
database is totally bizarre and the isc codes are not stored - they
are computed at build time and output to firebird.msg in some strange
binary format. You can download a gbak of messages.fdb from the CVS tree.
My listing is repeatable. It's 3 years since I built it. As I
recall, I did it with a series of stored procedures and output the
strings to an external table in a format that Word 7 could convert
into a table. You can export Word tables as Excel spreadsheets.
As I'm in the process of writing a Fb 2.0 supplement for The Firebird
Book, I'm due to be raking over that stuff in the near future and
should probably put the DDL for the stored procs somewhere in the
download area. I can't recall exactly, but I *might* have put them in
the downloads that you can take from the Apress website, on the page
for the book.
restore it in the v.2.0.x server and you'll have a v.2.0
database. However, if it is a Dialect 1 database, it will still be a
Dialect 1 database, with the same gotchas and limitations.
./heLen
>Hi guys,Then all you need to is run the command-line executable from the \bin
> I would like to know a dependable (version 1.5,2,^) resistry
>string that points to the firebird directory.
directory of your Firebird installation. It will install the
Registry keys and then all you need to do is export them.
> i would also love toYes to the first, no to the second. The PDF doc that is available in
>know if there is a database/excel sheet of firebird error codes (not a
>pdf or static document).
the documentation area was created by me from the v.1.5.2 messages
database. It's not a straightforward query at all, in fact the
database is totally bizarre and the isc codes are not stored - they
are computed at build time and output to firebird.msg in some strange
binary format. You can download a gbak of messages.fdb from the CVS tree.
My listing is repeatable. It's 3 years since I built it. As I
recall, I did it with a series of stored procedures and output the
strings to an external table in a format that Word 7 could convert
into a table. You can export Word tables as Excel spreadsheets.
As I'm in the process of writing a Fb 2.0 supplement for The Firebird
Book, I'm due to be raking over that stuff in the near future and
should probably put the DDL for the stored procs somewhere in the
download area. I can't recall exactly, but I *might* have put them in
the downloads that you can take from the Apress website, on the page
for the book.
>I am also trying to find a good guide toIt's toooo easy. Backup the 1.5.2 database in the 1.5.2 server,
>converting my database to version 2(any suggestions?)
restore it in the v.2.0.x server and you'll have a v.2.0
database. However, if it is a Dialect 1 database, it will still be a
Dialect 1 database, with the same gotchas and limitations.
./heLen