The problem re. Access paths is a windows only issue. and from memory it is
specifically linked to the Windows Local Access Manager
For performance reasons, when SuperServer first came to life (4.2) an inter
process shared memory (IPS) mechanism was built for InterBase on windows.
It was thought that this could laso be used on Unix platforms at a later
date, rather than the current mechanism that forces every user, local or not
to use remote.
The LAM can and does get confused in certain situations. If for example two
different local connection strings are used to access the database e.g.
myserver:foo\bar.gdb
\\myserver\d:current.gdb
InterBase sees these as two connections to two different databases..... I
don't think I need to explain what happens next :-)

There are no issues re. Unix and symbolic links, InterBase just parses and
expands the symbolic link as it should, the same is true for logicals on
VMS.

Regards
Paul Beach
Main Tel (UK):+44 (0) 1844 354465
Mobile: (UK): +44 (0) 7764 188603
http://www.ibphoenix.com