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


On Fri, Mar 4, 2016 at 3:13 PM, John Montgomery <jhkmont@gmail.com> wrote:

Thank you to everyone who replied to my query, A01, A02 etc works, I am
very thankful for that. Now the problem to prevent duplication, I have
tried several ways but obviously what I am doing is incorrect as it doesn't
work.


Hello John. I am thinking that you are seeing duplicate grave numbers? If
this is correct then I suggest creating an index for the grave number
column and selecting the option that the index be unique.

That constraint, unique, will prevent duplicate entries. It will also
prevent successfully creating and saving the index as long as there are
duplicates in the grave number column.

So first make sure there are no duplicate grave numbers in your table (that
includes grave numbers that have not been entered, e.g. blanks). Then
create the grave number index being certain to select the unique property
for the index. Save the change and it will no longer be possible to save a
record with duplicate grave numbers.

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