At 07:51 PM 14/11/2008, you wrote:

>Dmitry Yemanov wrote:
>>> I was under impression that if more then ONE database client is using
>>> SAME database, that all connections must go through TCP layer
>>> (localhost or remote) to ensure database stability
>>
>> This is wrong impression.
>
>This WAS the case at one time because of problems with 'path' in windows?

It never was the case.

>But that has now been eliminated?

The *problem* that existed in InterBase was that Windows allows different path formats. InterBase did nothing to stop different connections being made with different path formats. The server thought the clients were connecting to different *databases* so any writes had the potential to corrupt the database hopelessly.

It was solved loooooog ago (during the pre-Firebird 1.0 Beta cycle, AFAIR; anyway, so long ago I don't remember!) Firebird won't allow *any* connection where the path is different to the path used by any current connections. As to "eliminated" - no, if your applications (or anyone else's) are passing file strings instead of using aliases, then passing inconsistent path strings has the potential to lock someone out.

./heLen