Sage 100

Someone posted a method to find corrupt dates in MAS, does anyone recall the technique? I've been searching bad or corrupt date terms here, but cannot find it. TIA

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).

Thanks Wayne, that's it.

Wayne wins!!!

Check off or Check on? My ODBC setting is NOT selected by default.

Check it on.

I noticed that even with this setting on, if you try to import tables into SQL, it will choke on ""12/31/5999"" because the date/time in SQL is by default ""smalldatetime"".

Checking ""NULL Date"" didn't work for me as these invalid dates came into Crystal as blank which makes them impossible to isolate. Nor did ""Set Null to Default"" help or any combination thereof. I used this VBScript instead. Works like a charm.

Not being a VBS wizard, in the past I used VI to export the dates into a csv then used the find feature. What I found was that there was usually a space in the date.

Using V/I to export AR Invoice History of many clients might take until Romeny wins the White House.

Just had to resolve an Invalid Date Contents issue with a custom S/O report. Enabling the Null Date setting on the ODBC driver didn't help us in that it just showed a blank date (which we realized after-the-fact), but exporting the data via VI and pulling it up in Excel did. Then rather than fixing it via DFDM, we just re-keyed the bad date in S/O Entry - which appears to look perfectly fine on screen.

I have used VI also in exporting it as a text file.