We have a canned manufacturing package where users often requests reports via Date Ranges. The way the dates are validated are by using the CVTDAT command from within CL. We just experienced a flaw in the logic where it will allow an improper date range due to the CVTDAT logic. Here is the senerio:
On the Report Submit screen, the user mis-keyed the following:
Beg Date: 02/22/40
End Date: 03/27/04
The CVTDAT command converts the Beg Date to (19400222) and the End Date to (200402327) which allows the dates to pass and then the RPG program bombs out because the buckets are not big enough to handle the calculations.
This logic is throughout our entire system. Does anyone have a suggestion to correct this problem other than modifying every CL that validates dates submitted for reports? There are many! Any input would be appreciated!
Regards ... sulzener
Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.