Re: backup fail, how to prevent happening again

>  2004.2 win 2000 server xp clients
>
> thanks Spenser ,
>
> that's very helpful and good to know you are doing this (forcing the
> clients to quit prior to backup)
> and that it works..
>
> I've had a look at the command you point to - and this looks like the way
> forward
> http://www.4d.com/4ddoc2004/CMU/CMU00648.HTM
>
> if i have this in 'on Startup' - this will run when each 4d client is
> started up
> so i will know who is logged in. - as you described. so there fore the
> clients  i should force quit
> before the backup.
>
> i just wanted to reassure myself on  an important point.
> my only concern now is the use of a forced 'Quit 4D' for the client
> possibly in mid transaction.
> eg mid  record edit
> is there a possibility that the data file could be damaged if they have a
> form open within a transaction
> or will the system gracefully 'roll these back' ?
> I assume it will - as that's the point of a transaction
> or should i attempt to quit each process on each client ...
>
>
>
> .
>
> thanks
>
> john
> john convey
>
>
>
>
>
> John,
>
> Register Clients and you can count them with Get Registered Clients and
> instruct them to self-terminate with Execute On Client("@";"MyQuitMethod")
> `MyQuitMethod
> Quit 4D
> `end
>
> We Register Client, On Startup with an interval of 10.  And, On Backup
> Startup lets you cancel (just return non-zero) so we put up a dialog (click
> to cancel backup) for 30 seconds before proceeding.
>
> -spencer
>
> **********************************************************************
> Register for 4D Summit 2009 Today
> Early Bird Pricing Ends August 28th - http://www.4d.com/summit
>
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://www.4D.com/support/faqnug.html
> Archive:  http://lists.4D.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4D_Tech-Unsubscribe@...
> **********************************************************************
>