Erik,
I read an article on the web about Filemaker networking that said it
shouldn't be held in a file on a server to run as the host. The primary
reason was that if the server failed and closed filemaker
inappropriately, like a power shutdown, you will have an unrecoverable
filemaker file. a disaster you would agree. It was recommended to stay
on one of the workstations as the host. I do this, but have it backup to
a file on the server each evening when the host machine is closed.
Erik Wegweiser wrote:
Lee:
Absolutely! If FM Server is out of the question (though it shouldn't be),
you should dedicate a host machine, server or otherwise, that is not
a daily / multi-use workstation as your FileMaker Peer-to-peer host.
You haven't run into all the classic complications -- some hazardous -- that
can occur when
a person's workstation is the host?
As for remote access, if you have port 5003 open on the firewall/router
and forwarded to the host machine, everyone can log in from outside the office,
using FileMaker Pro. Otherwise, you can use the remote desktop application
of your choice for users to use their own desktop machine and the copy of
FileMaker Pro already there.
HTH
-- Erik
Hi,
I have a client who has a small office running one of my solutions. Currently
they run the solution off one computer while the other 3 use it peer to peer.
It works very well and I have it backing up to their server when they close the
program each night. The question was asked would it be better to have it
running on their server and the 4 machines that use it all work peer to peer
from the server. Its not worth them buying the server version for only the 4
machines that may use it. They're using Mac's running 10.4.7 and FM 8.5 One
person did ask could they use it at home. Currently, I access it using Timbuktu
to make updates. Could anyone enlighten me if there is a better way to improve
this set up.
--
Lee Mills
--
