N.B. if you are storing attachments in your table(s) you may find that either it gets very slow relatively quickly, or worse, so over-bloated that it bogs down due to file size as opposed to the amount of data you actually have stored in it. If those attachments are high res images, you might even exceed the max limit for a table size before too long. Usually, it's best to create and use hyperlinks to files instead (an image can still be shown, it's just not stored in the db).
I might also be seeing
- use of a memo field - do not try to link it to any other table field
- free form data entry for things like account/company data; a sure way to 'lose' data when looking for a record for SAMSON when it was entered as SAMSUN.
I think you made the all too common classic mistake of making a form or report instead of a query that produces the correct results first? If you cannot edit data in a query for a form whose purpose is to allow edits, or cannot get the correct data back with that query, it's no good. The form/report is the cart - one needs to put the horse first.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.