On Apr 21, 2:13 pm, d-42 <db.****s...@[EMAIL PROTECTED]
> wrote:
> On Apr 21, 8:40 am, Chris <driz...@[EMAIL PROTECTED]
> wrote:
>
> > Hi all,
> > I have a FileMaker script that closes a series of shared databases. I
> > run this script early in the morning before I do a backup process. I
> > have found that if someone is using the shared file (left it open
> > overnight) then FileMaker will pause the script, and display a pop-up
> > window that allows you to ask the person to close file, or cancel.
> > Since this is run early in the morning, I can't actually monitor this
> > pop-up window and press "ask". I was wondering if there was a way to
> > get FileMaker to automatically "ask" or to close the file regardless.
> > If you press "ask" it gives the user 30 seconds to close the file.
>
> > Any help would be appreciated, thanks!
>
> It may be time to look at filemaker server. It can do automated
> backups without shutting everyone down. I realize that's probably
> pretty steep just for unattended backups, but it may bring other
> benefits. If you are running an older version of FM, there are usually
> bundles available that will get you upgraded to 9.0 and include the
> server for next to nothing, and that might be a route to consider.
>
> Something to look into, and probably worth it if you have more than
> just a couple people using the database.
>
> -cheers,
> Dave
We have FileMaker server but we're verging on our database limit (over
100) We are helping a group migrate their 28 databases into a single
solution, but in order to do that we had to convert from FileMaker 5.0
to 9.0. After doing that, we wanted to utilize the file sharing
FileMaker has built in. Everything works okay, and I don't think it
would cause too big of a problem if the database was left open
overnight during the backup process. Just checking to see if anyone
ran across this problem.
|
