Tech Forum

One of our wards accidentally rolled the computer date forward while looking at the calendar (viewing the time in the taskbar, something around 6/20/2012). They didn't realize this until after entering and transmitting the batch in MLS.

Since that time (two weeks ago) they've tried unsuccessfully to correct the system time, but MLS will then generate an error because it thinks it's 3 weeks 'behind' when it sees the current time. They've 'back-dated' batches in order to transmit tithing.

I'd really like to get the machine time set to current, and MLS to recognize this as the current date. Is there a configuration file or registry setting I can change to bring MLS back from the future?

jcoleymail wrote:One of our wards accidentally rolled the computer date forward while looking at the calendar (viewing the time in the taskbar, something around 6/20/2012). They didn't realize this until after entering and transmitting the batch in MLS.

Since that time (two weeks ago) they've tried unsuccessfully to correct the system time, but MLS will then generate an error because it thinks it's 3 weeks 'behind' when it sees the current time. They've 'back-dated' batches in order to transmit tithing.

I'd really like to get the machine time set to current, and MLS to recognize this as the current date. Is there a configuration file or registry setting I can change to bring MLS back from the future?

You can't do it all at once, without going back to a backup from before the time change, which would require them to redo all the work that has been done since then. That's a mess, and requires help from Local Unit Support.

Since they're only off by 3 weeks, another approach has less impact. Each time you go to use MLS, set the clock back to the date MLS was last used (or the day after, depending on the time of day). If you only use it once a week, you can correct 6 days each week. The key is to make sure that the system date/time is just a little later than the last date/time that MLS was used.

See Changing the system date in the wiki for some additional hints, including a preventative measure.

This is a good reminder to tell all users to never adjust the system time and date. Maybe some don't know how much trouble it can cause, especially if you've had a lot of "staff changes" lately.

We've avoided this problem (by luck or by design) by posting a traditional calendar on the clerks office wall each year, in a place where the computer user can easily see it.

Thanks, folks. I'll let the bishop decide which route he'd like to go.