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

I don't know if it works in your case, but perhaps using A01, A02 … A10 will give the right order?

Den 02.03.2016 20:07, John Montgomery skreiv:
Dear Sirs,
I am trying to assemble a simple graveyard database but am having
difficulty in getting the form to work as I want.
I have tried to use parts of the "Search and Filter" database but end up
confused. I have also read relevent parts of the Base manual.
I have two forms, Graves and Burials, the Graves form covers ownership and
registration of a grave and includes a photograph of any headstone which
may be on site.
The burials form is mainly for burial record keeping.
The reason I have decided on two forms is that it allows me to see all the
relavent data in one screen.
Some specification criteria:-
In both the "Graves" and "Burials" forms Plot No., Headstone and owner are
to be common.
Plot number is the primary key and therefore cannot be duplicated for
obvious reasons.
The graveyard is laid out in rows eg A to Z. Each grave in each row is
given a number in sequence, eg A1, A2, A3 etc.
My problem arises when I enter double numbers eg A11, A20 etc, these should
follow in sequence but do not follow the sequence I want but A10 follows A1
How can I ensure correct sequencing.


To unsubscribe 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.