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


Both of these will be easy to do as a query in Base, although the 
first is a little tedious, provided that you can get both tables into 
the same database.

Something along the lines of

    SELECT * FROM <MasterTable>
        JOIN <MonthlyUpdateTable> ON Master.IdField = Month.IdField
        WHERE   Master.Column1 <> Monthly.Column1
            OR  Master.Column2 <> Monthly.Column2
            OR ... (The rest of the fields)

If you can't get both into the same database, don't use the embedded 
database (though you wouldn't anyway, would you? ;-) ), And bring 
them into separate databases and then perform that SQL using the data 
engine itself, ie not through Base, even if you use Base to get the 
data there in the first place.

For any database worth its salt 2000 records is tiny.

For records in one but not in the other

    SELECT * FROM <One version>
        WHERE IdField NOT IN (SELECT IdField FROM <Otherversion>)

And then do it the other way around.

Regards
Mark Stanton
One small step for mankind...



-- 
For unsubscribe instructions e-mail to: users+help@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.