Hi Lois I would suggest that the model in this case holds all the events needed to be displayed in the view. The view is just responsible for showing the calendar, bound to the events retrieved from the model.
I would probably create a Calendar page type with a property for setting the date range (maybe 2 properties a start and end date). This page type could then be used for the current events and archived events. Also if you had a requirement to only show events for the current month this would still work.
The Calendar page controller is then responsible for filtering the events by date range, binding this to the model and then presenting the view.
I agree with Janaka's solution, if you have the same presentation for the two views (with the only difference being the dates represented in the view). This would be a more flexible solution since you can feed in different dates to get a list of events.
However, if the presentation/html is different for archived page or you need to have a different URL (for deep linking, SEO or other purposes) then:
I am Quite new to episerver, I have a solution that has an calender page. We have created a model and view (which holds a list of all the events) the view shows the events from this year. Now we would then need a archive page which would show everything else in the list. It would need to go on a sperate page.
How could i use the same model (events) but use a diffent view?