I am having difficulty sharing ebase over our Peer to peer network. I've been reading the posts, but now have more questions than when I started. How can a remote computer access any of the files on my (host) computer without my sharing the folder? I have changed all of the files within ebase to multi-user, except the red ebase intro file - which doesn't allow me access to sharing properties. When I try to access the ebase.103 file on a remote computer(via a shared folder on the network) it says the file is either set as a single user or the host cannot be found. Ebase is open on the host computer, from what I've gleaned from the manual the host computer should be running ebase prior to any remote access. Any advice?
Date: Tue, 8 Jan 2002 21:50:15 -0500 Author: "Walt Daniels" <[EMAIL PROTECTED]> <mailto:> Subject: RE: multi-user ebase -- how's that data moving around, anyway? Body: > > 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 ---------------------------------------------------------------------
