Sage 100

Is it me or are others getting calls regarding the fat fingering of dates?? I have had several plus I must admit, did one myself last night cleaning up the BLS books for the tax man. What is frustrating is that I changed the module date to 12/31/14 but when I went to update the register, changed the date with just the month and date (e.g. 1224) which assumed the system year of 2015. Wouldn't it be better (wiser, logical) to pull the year from the module date, not the system date. Back in the day when you COULD change the system date, this wasn't an issue. But now it is. Other thoughts? Yes, this is Sage so what is the big deal. Thinking out loud....

I have seen more issues where the date itself is corrupt and then it throws that cryptic error message when trying to print a Crystal based report.

That is a different issue that STILL needs to be resolved. My beef is that the default year for updating should be pulled from the module date, not the system date. Unless you have made it a habit to type MMDDYY in all your date fields.

Only had three customers with date issues so far this week.

Just 3? It's still only Tuesday.