in my experience you get corrutions when you use different connection
strings from different hosts. in fact it doesn't matter if you're connecting
from different hosts, but it does matter if you use different paths. you
should always check this by looking at the open databases (which can be
listed for example with ib expert). one database should never be listed
there multiple times.
i for example had the problem with:
servername:/opt/interbase/databases/db.gdb and
servername://opt/interbase/databases/db.gdb

it seems that on linux (probably all unixes) you can avoid this problem by
creating a symlink to the db and always using this symlink. fb will resolve
the symlink to the original file name which will guarantee that always the
same path is used.

regards
mw

-----Original Message-----
From: rodbracher [mailto:rod@...]
Sent: Tuesday, October 15, 2002 12:43 PM
To: ib-support@yahoogroups.com
Subject: [ib-support] Re: Connection Strings


I use IB6.0 - does this mean I could get a corruption with local vs
remote connections ?

Or were the corruptions you were talking about only on different
remote connections ?

--- In ib-support@y..., "Jason Chapman (JAC2)" <jason@j...> wrote:
> I have never had a problem with local vs remote connections,
although for a
> couple of years now I have always connected remotely, even on the
same
> machine. On FB now, there should be no problem as the file is
locked on
> first connection, the problem used to be that if IB didn't realise
that the
> DB was already open it would merrily open it again and internally
think it
> was looking at two DB's, resulting in near instant corruption.
>
> we had it with:
>
> server:d:\data\some.gdb vs
> server: d : \data\some.gdb (notice the spaces).
>




To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/