Hi, I have a couple questions regarding recurring events in the evtns module (4.00.02)...

1.  Is there any way to create a recurring event with no end date?

2.  If a user opens the event details of a recurring event and clciks the "send notification" link, does this enable a notification for that single instance, or will the recieve a "recurring" notification as well?  If the notification is not recurring, is there any way to make it so?  I would kind of hate to have to tell my users they need to click the notification link for all event for say a weekly recurring event.

Thanks,

Scott

Thanks Roger,

The end date wasn't a huge issue, because like you said, I set events with a realtively far out end date.  Hopefully 5.0 will help with both issues. 

For now, I am working on a stored procedure that I added to the DNN database which essentially gets all notifications marked as sent for events marked as recurring and changes the "SendBy" date to the next occurance of the event, using the repeat criteria and notification criteria.  It then sets the "Sent" flag to false.  I'll just schedule it to run every hour or something.  Not pretty, but should hopefully fill the gap.

A question regarding verion 5.0 of the module.  Will it run on the current version of the DNN core, or will it require an update to the DNN core as well?

Thanks,

Scotrt

Sorry, I found the answer to my pervious question about the required core for verion 5.00 of the events module.  However, I have a new question.

We have just started using the events module ( I think we currently have 2 events in it).  With the database changes in 5.0, will the old db be completely updated, or will I have to go through and fix up the details of any events entered pre-upgrade?