The whole thing is an arse ache. Great Ouse Boating Assoc has had two terrible years with ill/dying committee members, data lost, muddled and bank accounts suspended. The latest cock up was the Direct Debit list was sent to the bank to draw down members subs. A copy of the list went to me (ex-membership sec but helping out as both my replacements have resigned in hurry due to ill health) and the Chair. We have been updating the membership record showing who has paid based on that list. THEN we were told actually 178 were declined (many members having given up, retired, died or figured out how to pay online!) But not which were declined, just a new list of those paid. So the task was to subtract one list from the other to discover who had not. Now I have undo many updated records of people who are not really members, or who paid by other means. Then I'm resigning again!
Thanks for trying to help all of you. I tried to learn SQL in my 50s. 70 in 3 weeks and can't be arsed to try again.
Phil Thane www.pthane.co.uk Tweet @pthane 01767 449759 07582 750607
On 29/03/2022 16:17, Chris Green wrote:
On Tue, Mar 29, 2022 at 03:32:57PM +0100, Bev Nicolson wrote:
On 29/03/2022 14:42, Chris Green wrote:
On Tue, Mar 29, 2022 at 11:39:34AM +0100, Phil Thane wrote:
Database nerds look away now.
I hate to say it but the obvious answer is that the data shouldn't be in a spreadsheet! :-)
If Phil ever needs to share it though, Calc will be easier to work with because Base remains incompatible with MS Access. Otherwise, yes.
Don't use either Access or Base, the GUI just adds complication and complexity.
Export to CSV, import into a sqlite3 database and write a one-liner in sqlite3 CLI to get the result you want. It might be worth using something like sqliteman to do the CSV import but otherwise just use command line.