Jason,
Good Question. My memory isn't that good so I'll have to do a little
digging to find my original source for this. It is partially covered in
the File Management Best Practices document on the Technet site. See
the link below.
http://www.filemaker.com/technet/members/resources/downloads/file_management_best_practices.html
Check pages 5 - 7. This document does indicate that you can manipulate
dbs on the fly but recommends a more conservative course. I'll do some
digging and see if I can find where I read this originally. When I
find it, I'll send it along.
Best regards
Bruce
Jason L DeLooze wrote:
Hi Bruce,
Where did FileMaker, Inc give this advice (updates to databases be
done off line)? Is this advice in some Knowledge Base article or some
other documentation?
Best wishes,
Jason L. DeLooze
Annapolis, MD USA
On 5/4/08 at 9:41 PM -0400, Bruce Herbach wrote:
Hi Jane,
Here is the grain of salt. They don't say you can't do it, just
that it's not recommended. I have on several occasions made small
changes to layouts and scripts on the live database. I try to do it
late in the day when they number of available users is small. So far
I have not run into any issues with the database or complaints from
users.
If I have to make a substantial change to one or more layouts,
scripts etc, my procedure is to do all of the updates to the database
then create an empty clone. Take the running version down, extract
all of the data and import into the clone. Verify the data and then
put the new version back on line.
For the most part I do this type of change over a weekend when the DB
can be off line with out to many complaints. I have had a few rush
changes where it was done in an evening.
Best regards
Bruce
Jane Reeder wrote:
Re: calculations via related field issues 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]>
<mailto:[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]>
<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.)
