Now I'm going in search of some backup software I can distribute with a
runtime solution. I was naive to think users would take the initiative to
create their own backup strategy; some do, of course, but enough don't to
make the issue a real problem.
"DB" <someonesomewhere.com> wrote in message
news:Jl5Ta.483956$ro6.11632546news2.calgary.shaw. ca...is> "Save a copy as" is safe.
> However, for the solution your looking for: FM Servers scheduled backupsServer> what you want. Simply schedule FM to backup the hosted files to a backup
> folder(s) every hour... or 3 hours... or whatever is appropriate. FMsafe,> 'pauses' files to back them up; does it remarkably fast, is completelyon> and is typically completely transparent to the end users.
> "Bill Jaynes" <bjaynesmontanaport.net> wrote in message
> news:bfida7$ok3$1balder.stud.idb.hist.no...> mid-save.> > Hello,
> > I've been reading some posts from the archives; need to learn more about
> > making backup scripts. One point I see made..
> > -Don't back up open FMP files. Problems can occur if Filemaker is> > What about the "Save a copy as..." step? If Filemaker runs that stepthey> a> > file could it be caught mid-save and save a corrupt copy? Or is that one
> > reliable method? I'm thinking for careless users who don't save to
> > removeable media, this could be useful. When they call with problems,> them> > could be directed to a folder where automated saves can be found; have> of> > rename the copy and move it to the working folder. Given the limitations>> > such a method, could it be reliable as far as it goes?
> > Thanks to Lynn & Christoph,
> > --
> > Bill Jaynes
> > Swan River Software
> > 406.837.4132
> > [url]http://www.shesmylittle.com/index.htm[/url]
> > [email]sales_nobolognashesmylittle.com[/email]