|
Rajan.Srinivasan@Allfun.com wrote: > > Thanks Jerry It works fine. I can able to take out one more statements > out. > > There is one more point I did'nt mention. > > > 1. Moving the numerical value ( 8, 0) to DATE STAMP Field with > (> Date format *USA) > > On the above statement, by any chance if there is some invalid date like > Februry 30, then > the program is boming out with run time message. > > For that , before executing the above statement, I am evaluating for > invalid date which runs almost 10+ statments. > > Is there any better way for this. > > Thanks again Yes there is. *USA Test(d) Numdate 99 The indicator in column 73-74 will be on if Numdate is an invalid date. Watch out, if Numdate contains 0 it is also considered an invalid date. -- ___________________________________________________________ Jerry R. Keppler Pattonville School District Computer Programmer 11097 St. Charles Rock Road (314) 213-8045 Voice St. Ann, MO 63074-1509 (314) 213-8650 Fax mailto:kepplerj@pattonville.k12.mo.us +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.