Hi,

> I can only take a SWAG at it and guess that the problem has something
> to do with WinXP. Besides prohibiting me from using IBOConsole (which
> was recommended to me as the best tool), the error is not fatal.
> However, I do feel a little leary switching to a database on which I
> have received such an undiagnosed error early on, as I am afraid it
> may crop up later after I have more invested in it. If anyone has any
> ideas, I would appreciate hearing them.

Well, I would say this isn't an issue of the database engine, but rather
of the client/admin tool you're using.

Firebird doesn't have a native/official GUI tool, only the command line
tools.

There are several 3rd party tools available, both free and commercial.

IBOConsole is a free one, so is IBAccess ( www.ibaccess.org ) or
IB_SQL (from www.ibobjects.com ). However, I do believe that
most people will purchase a commercial tool if they really want to
get down to serious work.

Try Database Workbench ( www.upscene.com ) and see if it works
for you. The license price is the cheapest around for all commercial
tools and a percentage of Firebird related sales at the website is
contributed to the Firebird project via a sponsorship.

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com