Subject Re: [firebird-support] Can not open FDB file
Author Helen Borrie
At 07:41 AM 17/11/2004 +1100, you wrote:

> > Hi,
> >
> > I am trying to create a FDB on two separate PC's. One PC is running
> > Win 2000 Server edition with SP 1 the other is running Win XP Pro.
> >
> > I first create a blank FDB on each machine. Under the same path, with
> > the same name, with the same user name, password combination,
> > following the same procedures.
> >
> > I then run the same SQL Script (contains schema and data) on each
> > machine.
> > The PC running Win XP Pro runs the script without any problems. Thus
> > at completion the FDB has tables, procedures, data, etc Perfect! The
> > PC running Win 2000 Server will not run the file. I am using the same
> > tool on both PC's
> > (isql) to complete the task at hand.
> >
> > The only difference between the two PC's is that the PC running Win XP
> > Pro has Firebird 1.5.X where the PC running Win 200 Server has
> > Firebird 1.1.X

Firebird 1.0.x? There was no Firebird 1.1. I'll respond on the assumption
that you are running a Firebird 1.0 release on the Win2K server.

> >
> > What could I be doing, which may cause this problem?

Can you connect interactively to the empty database with isql?

Have you checked that it is actually in the place where you think it is?

Are you trying to run this script remotely from the Fb 1.5 machine, i.e.
with Fb 1.5's version of isql?

Fb 1.0 doesn't support database aliases. If the script is using an alias in
the CONNECT statement, change it to the full path.

By default, Fb 1.0 creates a dialect 1 database. If the script contains
language features that are not supported in dialect 1, the script will
except. If you want to create a dialect 3 database, run the command SET
SQL DIALECT 3; before your INPUT command. (But this wouldn't cause the
message in your Subject).

Can't think of any other possibilities at the moment. The most likely
thing is something funny about the file path. Failing all else, drop the
empty database and include the CREATE DATABASE statement in the script.