Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

Hi :)
I think automating it creates problems.  Unexpected things tend to crop-up and it can be very 
annoying to find that your machine is suddenly outside of your control and running super slow at a 
moment when you need rapid access to deal with a situation.  

Where i 'work' we share the building with an organisation that only has part-time workers.  As soon 
as they sit down to do some work their machines hunt for updates and install them, run through a 
mysterious back-up process, defrags, does an anit-virus scan and error-messages pop-up such as 
"Must install new java now" and "Must reboot machine NOW".  After a couple of hours the machine has 
completed most of the tasks and is ready to use.  Just in time for the worker to have to go to 
their next workplace.  

The java updats never completes because none of them have an admin level account.  It gets almost 
all the way through and then drops out.

In our office we also have a lot of part-timers but when people login the computer lets them get on 
with work rather than forcing them to wait for the machine to service itself badly.  

Regards from
Tom :)

--- On Fri, 10/2/12, Ian Whitfield <> wrote:

From: Ian Whitfield <>
Subject: Re: [libreoffice-users] LO Base questions
Date: Friday, 10 February, 2012, 9:03

On 09/02/2012 18:53, drew wrote:
On Thu, 2012-02-09 at 17:12 +0200, Ian Whitfield wrote:
On 07/02/2012 20:08, drew wrote:
Periodically you should perform the following. When finished using the
database, open the SQL window. Menu [File>SQL] In the command window
enter: SHUTDOWN COMPACT You should, after a short while receive in the
status field the message: "1: Command successfully executed." At that
point close the file. [you must do so as the database engine is indeed
shutdown at this point] This will reduce the size of the file on disk
and the memory used at run-time, and will increase performance on
startup and shutdown. Depending on how actively you edit that table
this period can be once a week or once every two weeks..can't say what
is right for your specific usage.
Thanks Drew!!

This worked a treat for me and I can see a marked improvement in my
close-down times of the main DB and also closing Queries,

A real Gem!! (Is there any way of automating this do you know??)
Howdy Ian

Glad it helped.


As in a custom menu item for 'Close after Compact'
Every Friday compact the database?



Good question Drew!!!!! (thinking.......???)

I guess either would work but I think the first option would be my first 
choice. But rather 'Compact and Close'.

On reflection - whichever is the easiest to implement.

Ian Whitfield

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.