Corrupted Stacks

[Tom Glod]

I would change your save routine to save locally first, then copy to
network location.  That should prevent those kinds of issues.

On Tue, Jan 28, 2020 at 9:14 PM Richard Gaskin via use-livecode <
use-livecode at lists.runrev.com> wrote:

> Marty Knapp wrote:
>
>  > I have an app in which users create documents (stacks) that auto-save
>  > when they're closed. I have a a few customers who are getting
>  > corrupted stacks every once in a while. At least in a couple of cases
>  > they are saving to a network server or over an internet connection.
> ...
>  > Does anyone have any input with my shutdown routine? Ways of making it
>  > more robust?
>
> Save is save.  One command triggers the engine's save routine. Hard to
> get leaner than that.
>
> As a general rule, I would not advise saving large live documents over a
> network, or to any folder managed by network sync (Dropbox, iCloud,
> Nextcloud, etc.).  Tons of warnings from software vendors all over the
> web about things like that.
>
> Are the users able to recover from the "~" copy?
>
> --
> Richard Gaskin
> Fourth World Systems
>
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>


-- 
Tom Glod
Founder & Developer
MakeShyft R.D.A (www.makeshyft.com)
Mobile:647.562.9411