Thanks for your interest. I don't have hands-on access to the Windows 10
machine at the moment. I could probably get a copy of the file that
originally had the problem.
BUT, my last experiment was to create an entirely new spreadsheet file (just
a few cells, filled with arbitrary integers) on the Windows 10 machine, and
the Calc program wouldn't save that, regardless of whether I tried "Save" or
"Save as". So it seems unlikely the the original file was the source of the
problem. I believe that she has tried several files, with the same result.
One thing I will have to check back on is a few settings changes I made to
set up default file paths, and Windows file type associations so that the
user wouldn't be confused needlessly by a slightly different working
But, it still seems to me that a newly created file should be saved without
protest. If I made some errors in the configuration changes I made, I might
expect to have a little trouble finding where the file got saved. But I get
the error report pop-up immediately, as soon as I select any of the
available save options from the "File" menu.
View this message in context:
Sent from the Users mailing list archive at Nabble.com.
To unsubscribe e-mail to: firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy