I'm more/less the webmaster of a site for a dart league located in St. Charles MO. Our hosting company recently moved our site from a server in St. Louis MO to a server in Tacoma WA. It's time is PST/PDT; ours is CST/CDT. I recently developed a script that I wanted to run at 11:00PM CST every Wednesday, Thursday, Friday and Saturday. I set a scheduled task on my computer here to run it. Of course, 11:00PM CST is 9:00PM PST. And that's no good. I also have other scripts that write timestamped records to my database; these are written using the local time.
I asked my hosting company if there was anything that can fix this. He says no, I have to do the adjusting within my scripts. Seems to me that there has be some mechanism to adjust for differences in local time and site time. Servers can be ANWHERE in the world; people with websites on a server can be ANYWHERE in the world. I find it hard to accept that ALL those websites have special exception code to correct the time.
My scripts are written in vbscript and are NOT part of the asp.net environment. And, the site is set to the Central time zone in Admin I also believe that site was developed using the community version of DNN.
in re the system time problem:
I find it nearly impossible to believe there isn't a way around it. Seems to me that DNN has to provide some mechanism for it. Servers can be ANWHERE in the world; people with websites on a server can be ANYWHERE in the world. I find it hard to accept that ALL those websites have special exception code to correct the time. Especially when the website can be moved to another server. For example, what if I go ahead and fix all my code to adjust for the difference between PDT/PST and CDT/CST and you decide to move our website to a server in New Hampshire? Or Arizona? See what I mean?