so the "compare" is something you do in your head......it isn't a programming
function....
what you really want from the db is to look at data - and of course have it
organized.
the advice from the other person is good. there are a variety of online
tutorials for Access around the net you can google for.
really it comes down to defining your fields clearly i.e. contractor , task
(painting), cost, date, etc etc.
a single table is identical to a spreadsheet in many ways....easier to sort,
easier to filter, easier to make reports off of....but not as good for
financial calcs that run thru the whole system....
but a single table will may end up having you repeat the same info over and
over - depending on your situation. For example - perhaps in some place you
must have the complete Contractor's contact info i.e. address, tel , etc
etc..... you would not want to repeat that non-changing minutia with every
record of a job they do. In the Jobs Table you could just put their name or
maybe a unique ID for them - along with the task (i.e. painting) , cost,
date, etc..... Where over in the Contractors Table you have only their
complete contact info i.e. street address etc. These two Tables are then
cross referenced by the unique name or ID assigned to them. This is typical.