|
> ---------- > From: Buck Calabro[SMTP:mcalabro@commsoft.net] > Sent: Thursday, September 10, 1998 10:34 AM > To: 'MIDRANGE-L@midrange.com' > Subject: RE: *DATE data type on a DSPF > > On Thursday, September 10, 1998 8:28 AM, Leland, David > [SMTP:dleland@harter.com] wrote: > > Buck: > > > > Is this acceptable to you that the user has to correct the date even > if > > they simply want to return to the previous screen? > > Well, this is something I wrote for me (mini project management > system), > so the end-user doesn't complain too much! ;-) If it were in > production, > I'd have to say that it wouldn't be acceptable; it's too close to > having > CHECK(ME) fields. > > > Yes, I know that if I change my CA key to a CF, the program won't > die on > > me and instead it will force the user to correct the date. But, > that > > just doesn't seem right to me. > > I tried changing my CF03 to CA03, and I'm still forced to correct the > date > before I can leave the screen (I get the CPD406A message and the keybd > > locks.) How are you managing to leave the screen with an incorrect > date? > That's very interesting. I get the same message with an accompanying keyboard lock. But, if I press reset and then press F3 (CA03), I immediately get the RNX0112 program message. > The RNX0112 almost sounds like the RPG program is trying to update a > record with the incorrect date. I get RNQ0112 when I move an > incorrect > workstation date into a database date. Is the program doing some > processing when the user presses the Exit key? Perhaps you can avoid > the > processing, or use TEST to test the date field for validity before > moving > it? No, the program does not gain control until after the program message occurs, so I can't do anything like test for valid date, etc. What PTF level are you at? We're at TL98195. Dave > Buck Calabro > Commsoft, Albany, NY > mailto:mcalabro@commsoft.net > > +--- > | 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 > +--- > +--- | 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.