>
> Actually, it's still correct.
>
> "True local access" Windows-style: exactly and ONLY a client on the local
> machine. It will NOT work with a share or a mapped drive. Even for those
> who *think* they are connecting to a share or a mapped drive, it can't
> work. "Windows true local" works by emulating a network connection in
> shared memory space.
>
> heLen
>

Helen,

Thanks for clearing this up. I thought I remembered seeing something on
a mailing list indicating that the behavior for SMB and NFS was the same
WRT local/remote access. It seems to me as if the filesystem abstraction
should allow it to work.

In interests of causing trouble, is it likely that this behavior could
be changed to match the behavior under *nix? I think a lot of us using
the embedded server would prefer to be able to use any file accessible
by windows. Think of an "personal address book" application running off
somebody's "personal drive" on a server. Its VERY confusing for users
when an application works on a local disk and doesn't work on a network
disk.

I realize this is not the way its "supposed" to be, but the environment
an embedded db app runs is often very unfriendly to installing a
seperate server application.

--erik