Doug,

> Therefore, according to this you have to set the current drive and
> directory first, then call GetFullPathName. If you are going to do that
> then you might as well parse the file name yourself!

the whole point of using relative path names is to take advantage (!) of
the current settings, whatever they may be. If the server were to decide
by itself where to point (and how?) then it could as well reject
relative path specifications.

> Munging with the filepath that is sent from the client is not foolproof,
> however. UNC style filenames are completely different. They have no drive
> letter. Thus there are several canonical instances of filepath which
> properly refer to the same file and are not the same.

If I remember well, UNC filenames are currently rejected.

> The only problem I see (besides locking out gstat) of opening the GDB files
> exclusively is the possibility of the IB server process hanging up in some
> fashion which leaves the GDB file inaccessible until the server machine is
> rebooted. That would be very harsh and I don't believe we are far enough up
> the reliability curve to rule it out.

This would only happen on Win9x/Me machines; I don't think it's possible
with WinNT/2K to keep a file handle allocated by a dead process.
Ciao
--
____
_/\/ando