A user has just asked our 90 Minds group whether there’s an easy way to detect a bad date that is within a set of their MAS90 version 4.4 data.
Update August 27, 2018:
Sage has issued a Check Date utility for Sage 100 and Sage 100 cloud which can be run from recent versions of Sage 100 and automatically seeks out bad dates.
Download the CHECKDATE utility from Sage here. Place the download in your \MAS90\SOA folder and from the FILE menu select RUN and SYZCON.
Then RUN “CHECKDATE”
This utility prompts for your Sage 100 company code. It then scans relevant data files and places a file XXX_CheckDate.txt in MAS90\HOME\Textout\
This can be a very tricky issue to resolve mostly because finding the exact bad record is hampered by the fact that MAS90 or MAS200 will error out each time you run a report – or try to design a report to print the bad record(s).
That is — unless you know the secret setting that will allow the bad date(s) to print via a Crystal report.
If you’re wrestling with a bad date somewhere in your MAS90 or MAS200 files – here’s the solution that I’ve used before to quickly print out the data and find the bad date record:
Go into your SOTAMAS90 ODBC source. Check off “NULL Date”. Create a report in Crystal that draws from the file with the bad date. The bad date will no longer stop the report from processing. Sort by the date field. The bad dates will sort to the top (or end).
Now go into Sage ERP MAS 90 or MAS 200 (usually through Data File Display and Maintenance) and fix the bad record(s).
Note: Always backup prior to making any changes to your data through Data File Display and Maintenance. We are not responsible for damage done to your data.
