Sage 100

I have a situation where a client will fat-finger a SO Line Promise Date of 10/20/213 and it's accepted as valid data entry (should be 10/20/2013). I was surprised it's allowed. In DFDM it displays as 02130102. This causes a problem during subsequent SQL extracts that rightfully fail on a bad date record.

Doesn't surprise me at all. I've seen an upswing in bad dates the last several years, except mine usually contain a space, so they are 04 62013 instead of 04062013. Something is NOT checking these dates carefully enough at input time.

As a precaution, you can add a date range validation to these fields in custom office.

+1 @BillPfahnl http://community.90minds.com/2011/12/06/sage-mas-90200-quick-tip-from-zip-restrict-date-fields/

A simple script could check that the date is less than X days, months or years into the future.

Thanks for all the comments. I made the post more to voice the mildly unbelievable nature of the situation. I guess from a programming perspective the year 213 is valid. Really?

Everybody is working in direct sales (oops channel sales) cross selling into the base. They've eliminated the programming department and replaced it with the programmable calling department.

WADR - oh great now we have to create scripts to correct Sage program bugs...remind me again of what the customer maintenance is used for?

@WayneSchulz - the reminder you requested: maintenance is used to fund SageOne and X3

Why fund those when you could fund me?