Hi Jane,
After Jason asked about where I read the recommendation I sent you, I
went back and tried to find the source. The closest I came was the
File management best practices document I sent the link to last night.
It stated that you can modify live files on the server but suggested
using clones and doing changes off line.
So this morning I set up a test environment with an FM server, a hosted
DB and two clients in a small effort to duplicate your problem. I
opened the db on both clients and made changes to one of the layouts
using one of the clients. When I changed back to browse mode the
changes showed up on the other client in about a second or less ( as
expected).
I did the experiment a couple of times. Once using an Apple Dual 1 Ghz
G4 hardware server and once using a Virtual Win 2003 server. The
hardware server with a real 100 Mbit/second network was a little slower
to update. About a second. The Virtual server was only a fraction of a
second. In the case of the Virtual server all three systems where
hosted on my mac so there is no latency based on network and it had a
2.33 Ghz intel dual core CPU. So it was quite a bit faster.
So going back to your original issue, I would suggest looking into the
following:
-Is it just this client that is not seeing the changes? If it is just
this specific PC/client, then it is probably an issue on the PC. In
this case look at CPU utilization, disk space available. Also check
for viruses and other nasties that can load down the PC like it has been
turned into a bot.
- If many clients are having the issue, check the network load, CPU and
memory available on the Server. If the loads are high or the server is
low on memory and using virtual memory then this may be the cause of the
problem.
I hope this helps.
Best regards
Bruce
Jane Reeder wrote:
Hi Bruce,
That's a really interesting change of direction. I can't imagine
taking a database down every time I want to tweak a layout.
Thanks for letting me know.
J
On 5/4/08 12:40 PM, "Bruce Herbach" <[EMAIL PROTECTED]> wrote:
Hi Jane,
I did some research a while back on updating a database while it
is being served on a FM 9 server and found that Filemaker
recommends that updates to databases be done off line. They did
not say you couldn't update a database but that it is preferred to
update it off line and then put the updated database on line.
They don't list all of the possible problems, but if a user has
the database open during the update, it's possible that they may
not see the changes until they close the database and re-open it.
I hope this helps.
Bruce Herbach
Jane Reeder wrote:
I have a client where this happens on a regular basis. I
update a layout or
a field and the only way for her to get the update is to close
out her file
and re-open. Running Server 9 on a Windows box, mixed Mac and
Win clients.
Anyone else see this?
Jane
On 5/1/08 9:40 PM, "Sue" <[EMAIL PROTECTED]>
<mailto:[EMAIL PROTECTED]> wrote:
I also had the strange situation today of updating a layout
and revising a calculation on the server file, then having
the calculation work correctly on my computer connected to
the server, but another computer hooked to the same server
showed only the prior, incorrect calculation result. (In
this case all the tables referred to were part of the same
file and permissions were set to the same permissions group on
both computers.)
