|
Bummer, that's what I kinda figured. I agree, the single quotes surrounding values are kinda ugly. db > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx / Douglas Handy > Sent: Monday, October 25, 2004 2:57 PM > > Dan, > > > Oooh, in addition to all that, does using *CHAR vs. *DATE allow > > you to NOT have to surround a date value with single quotes? > > No -- that is a generic limitation of the command parser, not just the > prompter. For example, you can't specify this from the command line: > > CHGJOB DATE(10/25/2004) > > because 10/25/2004 is construed as an expression ( = 10 / 25 / 2004 or > about 1.996E-04). > > In fact, I ended up deciding to populate my POP-supplied dates without > separators just because of that issue. I still accept anything they > key, with or without separators, but didn't like the looks of the > single quotes within the command prompt panel. > > Doug
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.