I'd use one table for all incidents whether generic or serious. I can guess that a lot more data has to be recorded when the incident is serious, but I'd still use a single table for that data. You can either define additional fields for the serious incidents that are just left empty for generic ones or you can link in a related table for the serious incidents only, but link that to the incidents table.
This then allows you to set up a summary report which can be broken down into sub totals by month and by type of incident.
the following calculation field is useful for giving all records with a date in the same month/year, a common value so that you can sort to group them by month:
cMonth: IncidentDate - Day ( IncidentDate ) + 1
See this thread to learn more about summary reports: Creating Filemaker Pro summary reports--Tutorial
Thank you so much for the reply. I thought about having just one table for all incidents when I first planned the database, but decided to use 2 when I actually created it. I will change it to 2 and do some testing.
thanks again for your help.