Understand that you didn't design the database. Does that necessarily
mean that you aren't allowed to normalize it and get it in proper running order?
From your description, it would be relatively simple to normalize it
using three primary tables plus a lookup table:
tblPatient with fields:
PatientID (autonumber)
PatientName
+ other non-changing data items (e.g., DOB, Sex, etc.)
tblVisits with fields:
VisitID (autonumber)
PatientID (long)
DteVisit(date)
ProcedureID(long)
TblPatientsAndVisits 'this serves as the joining table
'between tblPatient and tblVisits
PVID(autonumber)
PatientID(long)
VisitID(long)
Finally, a lookup table of procedures
tblProcedures with fields:
ProcedureID (autonumber)
ProcedureName
With this type of structure, there'd be little problem returning
the information you're after. This approach is similar to the
StudentsAndClasses database template offered by MS.