Ahh, the multi-day dilemma, especially when it wasn't a total time event. Choice is simplify with one database and only have to make corrections to name, club, etc. in one database. But then have to deal with people who are running in different classes...
I have found it easier to stick with OE200x for events which don't require total time and when the events are going to lead to many people asking for different classes - like when you are doing a short day and a long day.
I am also a huge proponent of allowing people to change courses after the first day. At one of my first A meets, I was in over my head on the Green course and asked to move down to Orange for the second day. Despite my tears, I was turned down. Ever since then, I have tried to accomodate course changes for the second day of the event. I don't mind the extra work, if the maps and start times are available...
If I am using MT200x, I create a second entry for the person and change the SI card for day 2 of the original entry to a bogus number (usually add a 9 to the front of the real SI card number). I also add a number to the front of the original Start Number - 1 to signify that this was the Day 1 record. See the example
for the bottom two records for Wrenn Taylor.
I then go to Evaluate SI Cards and change the appropriate records to DNS.
You can issue a second SI card, but you still need to create a second record to get the class correct, so I think editing the original SI card is better.