No, you do not need to make a table for each case, but you do need to change your current structure.
I would have a table to hold the case information
tblCases
-pkCaseID an autonumber primary key field
-CaseNo
-fkCaseTypeID a foreign key to a table that holds the various case types
tblCaseType
-pkCaseTypeID primary key, autnumber
-txtCaseType
Then I would have a table to hold people related to a case. Since you have many people related to a case, you have a One (case)-to-Many (people) relationship which is captured in a related table
tblCasePeople
-pkCasePeopleID an autonumber primary key field
-fkCaseID a foreign key to related back to tblCases
-personName
-Role (client or opponent)
Each case will have many decisions. In your current table, you do not relate the decision to a specific case. This table will do that
tblCaseDecisions
-pkCaseDecisionID an autonumber primary key field
-fkCaseID a foreign key to relate back to tblCases
-decisiondate
-decision
-NexthearingDate
You will have to capture all of the decision details, but you can use a query to show just the two most recent ones in your form. But let's worry about getting your tables structured correctly first.
I've modified the database you attached previously. I've included the tables I described above and a form.
You might benefit from the
tutorials on this website