I think that error is always a bad date format in one of the date fields.  For example, you may have 01/01/201 instead of 01/01/2019.

I agree with BShockley, it is a bad date.

The trick often times is to find the specific record.

Try printing your bank reconciliation report using ranges of dates to narrow down the record to look for.  If you select through 6/15/2019 and it prints properly then your problem is after 6/15/2019 so keep extending the date out.  If it doesn't error than the problem is prior to 6/15/2019.   Keep adjusting your date ranges until you narrow it down to a specific record and then inspect it carefully with DFDM.

Thanks for the comments. I ran an VI job to export the br_transation table.

Found a date shown as "2019 201"

Noticed there is no TransactionDate either. seems like there should be. Will try modifying in the development system to see if it corrects the error.

I've seen that before... a space where there should be a zero padded month value.  DFDM edit should fix it.

Ok. The Bank Rec report now runs. Nice, and THANKS!

Joy short lived though. Now a new error "Error in file AP_AgedInvoice...rpt Database Connector Error 9"

My thinking is the correction I made (with your suggestions) to allow the Bank Rec to work, has another table that may hold a funky date.

The aging report runs on other date ranges eg (2/28/19), but fails when using date criteria "as of 1/31/2019". I don't see a table called AP_AgedInvoice...only a AP_AgedInvoiceWrk table.

Ideas??

Check AP_OpenInvoice...?  The AP Aged Invoice report pulls data from there... and possibly AP_TransactionPaymentHistory.

BShockley, TomTarget & Kevin M are correct. Database Vendor Code 9 is always due to an incorrectly formatted date. Javier and I (back in the day) worked on this KB which mentions a nice way to find the bad record using Excel: ID: 19509.

If you're not sure which table(s) you can always use the Custom Office trick to find out what tables make up a Standard Report in Sage. That would be ID:79539.

Sage released a utility to check for bad dates... KB 89700

CheckDate Utility for Vendor Code 9 errors

It certainly makes finding the bad record(s) easier.

You can also check the null dates check box in ODBC options of SOTAMAS90.  Then you can see the incorrect dates in Crystal or an Excel query

Just got back from vacation. Wanted to thank those who took the time to comment.

Also like the idea of looking at the reports to see which table sources are used.

The invalid/incomplete date was the culprit as described above.

Best