>
> FM Server clearly runs its own layer on top of whatever
> networking protocol
> is in use (frequently TCP/IP).  The files (e.g. ebase files) are opened by
> the server and shared to all the clients.
>

Yes, sort of, shared isn't quite the right word. FMP, the client, behaves
the same whether it is going to FMP Server or another copy of FMP acting as
a server. It uses the raw TCP/IP protocols.

> I'm curious what happens on a Windows network when small number of users
> share ebase (sometimes simultaneously).  Is FM depending on Windows file
> sharing to access the data?
No, and in fact sharing the files via window is a very bad idea. Basic FMP
PRO will try to use file access (thinking it is serving) if there is windows
sharing present.



> Can the database be shared without
> Windows file
> sharing?

yes, and is what should be done.

> Does FM still run something of its own network layer on top of
> whatever protocol(s) are selected?
>

If FMP builds a layer on top of TCP/IP, it is not exposed to users so one
cannot tell.

> Related question:  how does FM Server (or multiple simultaneous users
> without FM Server) deal with file synchronization to avoid
> corrupted/goofed
> up data?
>

It obeys appropriate locking protocols using TCP/IP.


-----------

The difference between how Server treats disk writes and now FMP is a
question of robustness of the code and appropriate caching and flushing of
the cache. The probability of data corruption on a power outage or program
check error on FMP is very high and on Server very low.



------------------ 
Reminder to each recipient: To change your list account preferences, go to
http://email.sparklist.com/scripts/lyris.pl?enter=support  and enter the email address 
you used to subscribe to the ebase support list:: [email protected]

To unsubscribe send a blank email to [EMAIL PROTECTED]
---------------------------------------------------------------------
 ebase - Relationship Management for Nonprofits, http://www.ebase.org
---------------------------------------------------------------------

Reply via email to