finished. allmost

[clean32]

ok

firstly, thank you all who helped

and attached is the almost finished product

need polishing but it works

when you all have finished rolling on the floor laughing at all the rules i have broken and how i have done everything the hard/odd.strange way.

you then can comment, constructively. i would welcome the input, that is how one learns.

Dean

 

[CJ_London]

So, quick glance:

spaces in table and field names,
fields called 1,2,3 4 etc - in addition to be likely to cause unexpected errors implies data not normalised
no relationships defined
fields appear to be randomly linked together (no name commonality)

makes it difficult to work out how it is supposed to work.

On the positive side you have avoided using lookup fields in table design

So at lease address the lack of defined relationships and provide a description of what it is supposed to do and how

 

[AccessBlaster]

and attached is the almost finished product

I built my first database 8 years ago, I thought I was finished with that project too.

Also no primary(s) key defined. No real way to keep dupes out, in fact dupes are allowed everywhere. Field names don't follow any naming convention, the ALL CAPS approach will get tedious to code.

Date is a Access reserved word and should not be used. Use something like DateCleaned.

 

[clean32]

I built my first database 8 years ago, I thought I was finished with that project too.

Also no primary(s) key defined. No real way to keep dupes out,.

did you like the way o found and deleted duplicates, have any better ideas?