Agree with June. You've not given us enough information in your description nor your database. You can't just jump into the issue you are struggling with and hope we get it--you must tell us in a very generic way what the real life situation is that you hope to capture with your database. No database jargon--just pretend you are telling a group of elementary kids what it is you guys do and how this database will help you.
After that, complete your database. tbl_Rules has no data and no real fields and you haven't completed the Relationship tool so we don't know how all this data is tied together. Do that as well.
Finally, from what I do see in your tables, you need to learn about normalization (
https://en.wikipedia.org/wiki/Database_normalization). The 2 tables that house most of your data are not properly laid out.
Here's the specific no-no's I see:
Duplicate tables --> tbl_IncidentDetails and tbl_VoucherDetails should be merged. They share at least 90% of the same fields, you can make the other 10% work in one table. For example, I see TemplateID in one table but not the other--when you merge them bring that field into the new table and just leave it blank if necessary.
Not properly using foreign keys --> You have tbl_StatusDetails which is fine and you even have an autonumber primary key in it (StatusId), which is great. But you don't use that autonumber primary key, instead you have 3 fields for Status information in both tbl_IncidentDetails and tbl_VoucherDetails. That is incorrect. You should only have StatusId in those 2 tables and not the 3 you have in there (STatus, StatusUpdate, StatusUpdatedBy). This is just an example, I see you have done this with a few fields (BankName/BankID;
Storing data in field names --> When you have multiple fields with similar names but prefixed/suffixed/numbered you need a new table. I see CorrectBeneficaryAC, WrongBeneficaryAC, ReversalCorrectionBenAC, etc. in tbl_VoucherDetails. Everything that comes before the 'AC' is data and should be in a field, not in a field's name. All those fields need to come out and go into another table (like you did with tbl_STatusDetails) and everything in the field name that comes before the 'AC' should go into a field called 'ACType'. Again, that's one example, you've done this a lot in your tables.
So 3 tasks--write an easy to understand overview of the big picture; read up on normalization; and work on your tables, complete the Relationship Tool in Access and post back a screenshot. Don't worry or even think about forms or reports, you've got a ton to focus on getting your tables correct.
