Some years back I was called to a new client that was running your
kind of setup, as they were unable to understand why their system was
so slow.
Also they had a problem with having to rebuild their databases
occasionally in order to keep them running.
As I started to look at their problem I found out they were using the
same setup you were describing.
The first person to open the database from the server got reasonable
speed while the rest got pretty slow speeds.
Also it sometimes happened that the person that first opened the
database files had problems shutting his/her machine down because of
other users being connected to the databases they were sharing.
The solution was to actually pull the plug.
You go figure what happened after that....
So after experiencing this I simply don't recommend this solution to
anyone.
Using FM server gives all users the same speed.
It gives you an easy way to back up your databases without actually
first throwing all users out first.
It minimizes the chance of data corruption since the data and the
serving mechanism reside on the same machine.
And using FM server seems to also minimize the chance of data
corruption when a client machine crashes.
Please someone correct me on this if I'm goofing off again.
On 20.2.2007, at 19:45, David Lynx wrote:
Whats interesting is that all our files here are stored on a
Windows server,
and everyone opens them up and shares them. Etc from their own
machine. We
have been doing this for years and years and have never had a
problem. We
were advised to take this route, rather than using Filemaker
Server, from
someone at Filemaker. It was less expensive, and it works great.
I just can't figure out why this other company can't do it.. Maybe
it is
because the file is not actually sitting on a server, but a client
machine.
On 2/14/07 1:57 AM, "Hans Gunnarsson" <[EMAIL PROTECTED]> wrote:
One of the reasons for this message is when the file is stored on
some kind of shared drive (file server) and not on that persons local
disk.
This should actually not be done since it increases the possibility
of data corruption and does have a tendency to slow things down
considerably.
Please make sure that the file is stored locally on one client
machine and that this machine is always used to start up the
solution.
Kind regards
Hans
On 1.2.2007, at 17:35, David Lynx wrote:
I went to another company in town to help them with their Filemaker
program,
but I was puzzled by something.
When we open a shared file at our place, the first person in the
morning
gets the message "are you sure you want to share this file" - its
annoying,
but it opens up other people to share it.
Although they have the networking on for that file, it does not ask
that
question. We were able to get another person to open the file, and
it asked
the question.
Then.. It started doing something weird later.. Even though
everyone had the
file closed, I went to another computer to open it remotely, and it
wouldn't
do it.
When you say open remotely. Do you mean using FM's "Open file dialog"
to open the data base from a mounted shared drive or pressing the
"hosts button" in the open remote window?
Is there something they don't have checked somehwere?
Probably depends on your answer to my question.
Hans
