Hi :)
We all get all messages to the list so you can respond to more than 1
person in a single post. If you are specifically talking to just one
person in 1 paragraph and then another in the next you could use @
signs, for example
"
@Tom blah, blah
@Jay blah de blah
@Everyone blah
"
I don't know why we don't do that sort of thing on this mailing list
but i've seen it a lot in other projects. I gather that gwibber or
twitter or something uses something similar for their main addresses
so it might get confusing for some people. Maybe that's why i haven't
seen it here much. Until my recent move to GMail i would only see 1
message at a time so i would reply to each individual one. It's
taking me a looong while to get used to the much more sophisticated
approach of threaded mailings but its' helped me cut down on traffic
quite a lot!
Since you are running into problems with the old spreadsheet might it
be worth considering
1. starting a fresh new one and then
2. copy&paste or import by Csv only the data you really need access
to most often and
3. keeping the old file as an archive to refer to.
I found that when moving from 3.3.x branch to 3.4, and again from
somewhere around 3.4.x to the next ones, sometimes weird little
hitches happened that were smoothed out by starting afresh. Maybe
it's because so many forks of LibreOffice merged at around that time
because i've not found similar issues with any upgrades since then.
Of course it could have been just my imagination or unfamiliarity with
LibreOffice because i hadn't used it much before the forking.
With Excel i found that spreadsheets over around 5 sheets tended to
become a but unwieldy (people couldn't cope with the tabs disappearing
under the scroll-bar or having the scroll-bar so short) so i would
either break them up (the spreadsheets, not the people) or convert
them to databases depending on which seemed more appropriate and/or
easier.
So there are 2 good(ish) and probably many other good reasons for
breaking up the spreadsheet but doubtless there are many good reasons
to keep all your data together! So it's just a suggestion that might
well not be possible.
Regards from
Tom :)
On 26 December 2013 14:31, Robin <rc.rattusrattus@gmail.com> wrote:
On 25 December 2013 20:39, Jay Lozier <jslozier@gmail.com> wrote:
Hi,
Does your spreadsheet have a large number of calculations and referrals
that periodically take a long time to run?
Thanks for the reply. Spreadsheet is simple but over 4 years old. There is
just a daily entry, calculation of cost of entry, monthly totals. There are
7 sheets covering different periods of time since 2009.
Also, can you post the spreadsheet to Nabble? Please do not post anything
proprietary or private.
I'll consider doing that.
Thanks
--
*rob*
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: 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.