Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.mobile.android > #154316

Re: Google calc trouble

From "Carlos E. R." <robin_listas@es.invalid>
Newsgroups comp.mobile.android
Subject Re: Google calc trouble
Date 2026-06-30 11:24 +0200
Message-ID <nahg9uF8cknU2@mid.individual.net> (permalink)
References <naetl1Fp983U1@mid.individual.net> <111vp0v$stoi$1@dont-email.me> <111vr5o$tgjf$2@dont-email.me>

Show all headers | View raw


On 2026-06-30 09:27, Chris wrote:
> Arno Welzel <usenet@arnowelzel.de> wrote:
>> Carlos E. R., 2026-06-29 11:53:
>>
>>> I have been using Google Calc spread sheet for some years, to track how
>>> much gasoline I buy for the car, and how many kilometres it does.
>>>
>>> Well, one day it lost me entries. It said there was some sync problem,
>>> maybe it had stored a local copy that did not match the cloud version.
>>> Now that file is impossible to open in the phone, it stalls. I could
>>> open it on the computer and save to a different name, but one or two
>>> lines are lost.
>>>
>>> It's done it again. Can't open the file in the phone.
>>
>> That's the reason, why we have a thing called "backup" ;-).
> 
> It's also a reminder that "cloud" is not synonymous with "backup".

How do you a backup of a calc sheet that is corrupted the instant you 
use it?

  * Open file, add a line.
  * File is corrupted, silently.
  * make a backup,
    · backup is also corrupted.

Do you do backups every 10 minutes, of the calc sheet files you edit, 
every time you save the file? On a phone, while driving?

Typically you do a backup at the end of the office day, or the week.

-- 
Cheers,
        Carlos E.R.
        ES🇪🇸, EU🇪🇺;

Back to comp.mobile.android | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Google calc trouble "Carlos E. R." <robin_listas@es.invalid> - 2026-06-29 11:53 +0200
  Re: Google calc trouble ram@zedat.fu-berlin.de (Stefan Ram) - 2026-06-29 10:16 +0000
    Re: Google calc trouble "Carlos E. R." <robin_listas@es.invalid> - 2026-06-29 12:37 +0200
      Re: Google calc trouble ram@zedat.fu-berlin.de (Stefan Ram) - 2026-06-29 10:53 +0000
        Re: Google calc trouble Andy Burns <usenet@andyburns.uk> - 2026-06-29 12:06 +0100
          Re: Google calc trouble Chris <ithinkiam@gmail.com> - 2026-06-30 07:27 +0000
          [OT] LLM-generated content in articles (was: Re: Google calc trouble) Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-30 09:03 +0100
            Re: [OT] LLM-generated content in articles ram@zedat.fu-berlin.de (Stefan Ram) - 2026-06-30 09:20 +0000
  Re: Google calc trouble Dave Royal <dave@dave123royal.com> - 2026-06-29 12:15 +0100
  Re: Google calc trouble Arno Welzel <usenet@arnowelzel.de> - 2026-06-30 08:51 +0200
    Re: Google calc trouble Chris <ithinkiam@gmail.com> - 2026-06-30 07:27 +0000
      Re: Google calc trouble "Carlos E. R." <robin_listas@es.invalid> - 2026-06-30 11:24 +0200
        Re: Google calc trouble Arno Welzel <usenet@arnowelzel.de> - 2026-06-30 17:33 +0200
          Re: Google calc trouble "Carlos E. R." <robin_listas@es.invalid> - 2026-06-30 19:19 +0200
            Re: Google calc trouble Arno Welzel <usenet@arnowelzel.de> - 2026-07-02 12:58 +0200
              Re: Google calc trouble "Carlos E. R." <robin_listas@es.invalid> - 2026-07-02 13:07 +0200
        Re: Google calc trouble Chris <ithinkiam@gmail.com> - 2026-06-30 19:56 +0000
          Re: Google calc trouble "Carlos E. R." <robin_listas@es.invalid> - 2026-07-01 12:30 +0200
            Re: Google calc trouble Arno Welzel <usenet@arnowelzel.de> - 2026-07-02 12:59 +0200
    Re: Google calc trouble Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-30 08:52 +0100
      Re: Google calc trouble Arno Welzel <usenet@arnowelzel.de> - 2026-06-30 17:34 +0200
    Re: Google calc trouble "Carlos E. R." <robin_listas@es.invalid> - 2026-06-30 11:19 +0200
      Re: Google calc trouble Arno Welzel <usenet@arnowelzel.de> - 2026-06-30 17:36 +0200
        Re: Google calc trouble "Carlos E. R." <robin_listas@es.invalid> - 2026-06-30 19:20 +0200

csiph-web