So I've built this db. to track persons and mainly their dates e.g. dates in, dates out, Courtdates, Applicationdate, baildates and the list keeps going in my mind; different TYPES of dates would have many fields in the table. to get around this I've tried a drop down list of types to case numbers affixed to Five [5] dates e.g. date_1 date_2 date_3 all up till date_5 making a personID on one record set i.e. row. but am encountering a slight anomaly; where person(s) just used one or two dates according to their case assessment making other fields in their record empty???. using the many to many relationship one person could have many dates and any given date type could have many persons.
Question, is this a good critical way of building this db.??, because IF I use the fields as dateTypes i.e. columns and not i.e. row or recordset we are looking at let say Courtdate many entries on that field maybe 1,000,000 entries and counting will access support this amount continuous and I will not have to split the db.
Question2, under formatting is there a way to color code the [date-text] not access conventional conditional formatting rules e.g. like in Excel any textbox the user could color code the text or field so I'm basically asking under dates_1 through _5 fields could I give the dates a color to mean type of dates affixed to dropdown list e.g. [SGIN 00011] their are like 8 types of this in a dropdown list with the many to many concept... HOPE u guys understand what am asking!