Alan,

I think option 1 is a better choice.  I'd put it in the module settings and just let people offset ALL the times for the modules by *n* hours. This would let them account for issues where they may have not set the local timezone when they update and not realize it until later. Once you explained to me what was happening it only took a few minutes to get the times I'd imported corrected. I'd provide that explaination in a readme and let the users correct times in mass as needed.

Brent...there is a bug in the current version.  Another early user discovered it.  I have corrected and am trying to get the module ready for the official DNN Project release. Thanks, Alan

Keith, that's an interesting idea.  How would the offset work.   If it was always in effect and they actually started using the TimeZone, wouldn't it corrupt other times?  What may be more acceptable is to put in a process that can adjust all unedited Events...I believe the TimeZone setting may be "NULL" if they are converted/upgraded events from previous calendars modules.