Our corruption on IB5.6 came from spaces in the connection string, I can't
remember where they were, but I think it might have been:
server: d :\drive\

or something like that.

Have they fixed it in 7 I wonder. Obviously it is fixed in FB Win32 as the
DB file is locked by the first connection.

JAC
""Thomas Steinmaurer"" <ts@...> wrote in message
news:FGEFIGLMFAKKKHHOJFHNKENFEBAA.ts@......

> Hi all,
>
> does someone know what InterBase treats as different connection
> strings, which can lead to database corruption.
>
> Surely, one combination is:
>
> c:databases\data.gdb vs. c:\databases\data.gdb
>
>
> But what about the following?
>
> - local vs. remote connection (IP address)
>
> e.g.: c:\databases\data.gdb vs. 127.0.0.1:c:\databases\data.gdb
>
>
> - local vs. remote connection (the "real" IP address)
>
> e.g.: c:\databases\data.gdb vs. 192.168.0.100:c:\databases\data.gdb
>
>
> - local vs. remote connection (server name)
>
> e.g.: c:\databases\data.gdb vs. localhost:c:\databases\data.gdb
>
>
> - local vs. remote connection (the "real" server name)
>
> e.g.: c:\databases\data.gdb vs. ntserver:c:\databases\data.gdb
>
>
> - remote connection vs. remote connection
>
> e.g.:
>
> 127.0.0.1:c:\databases\data.gdb vs. 192.168.0.100:c:\databases\data.gdb
>
> or
>
> localhost:c:\databases\data.gdb vs. 192.168.0.100:c:\databases\data.gdb
>
> or
>
> ntserver:c:\databases\data.gdb vs. 192.168.0.100:c:\databases\data.gdb
>
> ...
>
>
> Is it simply the missing '\' in the database path, or can database
> corruption happen when mixing local vs. remote connection.
>
>
> Just thinking loud (or am I bored?). Thank you.
>
>
> Regards,
> Thomas Steinmaurer
> IB LogManager 2.1 - The Logging/Auditing Tool for InterBase and Firebird
> http://www.iblogmanager.com
>
>
>
> 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/
>
>
>