on 4/11/01 8:26 PM, Philip Bowman at [EMAIL PROTECTED] wrote:
> All:
>
> We have recently made the leap and purchased FM Server 5. We find that
> connecting via the open > hosts > ebase.103 works for some
> of our clients (all clients running FM Pro 5) but others seem to be connecting
> the "old" way, that is, not hosted by FM Server, but
> directly to the files.
Don't, repeat DON'T let them do that. Remove file sharing privileges if
necessary - it won't affect FM Server to do so.
> These are the symptoms: 1.) Connecting the "old" way is painfully slow -
> maybe 3 minutes to open all the ebase files where as
> connecting through the host is relatively fast.
Yes, again, just don't - the "old" way is very very bad - okay?
>2.) When attempting to modify
> a table with "define fields", the machines that seem
> to connect correctly get a dialog that allows messaging other users to close
> that file, whereas the machines that connect slowly
> get the error message to the effect "Can't modify a file while being shared."
Correct - FM Server allows a single connected user to ask other users to
disconnect so that the database structure can be modified. This will not
work in a peer-to-peer environment (which is what's being created whenever a
user opens the files the bad "old" way).
>
> What more information do we need to diagnose this problem?
to solve the problem - force users to connect via "hosts" - by removing any
ability to open files directly.
colin
------------------
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
---------------------------------------------------------------------
