Sage 100

Does anyone know the underlying cause of the bad dates that get into the system occasionally, causing the Database connector error - Vendor code 9 ? we can find them and fix them (normally something like 2015 529 instead of 20150529), but we are being asked why they happen and how to prevent it ? Thanks.

64K question. Just a PITA to fix. If anyone does know, please let Sage in on the secret so perhaps they could fix it.

Building an object framework without putting proper date validation code in the base...

I know I was able to type a date in incorrectly once - I think I put in 03 515 instead of 030515 just to test and it took it. So yeah, not validating all possible issues (an issue since they started storing them as strings instead of dates).

Where is everyone seeing the issue. I encounter them mainly in SO Entry.

AP Invoice Entry

I've had numerous clients with bad dates from AP Invoices .. Sage bug no doubt.

I think I've seen it in cash receipts. People usually mention they were keying quickly. It's a similar issue to not disallowing people from creating new form codes. Half the larger sites have all manner of crazy forms because people made a typo into the form code field. Yet nobody at Sage thought that maybe the area should be secured? A big problem at Sage is they have practically nobody left with consulting/field experience.

Yup, had it in all of these entry screens from various clients. I was also able to type an invalid date. I would think this is an easy fix. Does anyone know a way to get Sage to recognize and correct (that actually works)?

Thanks to all who responded... not sure the best way to get this on Sage's radar....

Send a note to Deborah Nelson....