Re: Odd Date selection
- From: "dtsig" <dtsig@xxxxxxxxxxx>
- Date: 26 Mar 2007 12:59:49 -0700
On Mar 26, 12:42 pm, "Dale" <dale_bened...@xxxxxxxxxxxxxx> wrote:
On Mar 26, 11:51 am, "dtsig" <d...@xxxxxxxxxxx> wrote:sort invoices with order.date GE "03-14-07" and LE "03-17-07" by-dsnd
The Following works ..
SELECT AUDIT_SOURCE WITH chg_date >= "03-20-07" AND WITH chg_date <=
"03-25-07"
[404] 77 items selected out of 2116 items.
This one doesn't
select audit_source with chg_date GE "03-20-07" and with chg_date LE
"03-25-07"
[401] no items present.
the doc says that GE and LE are the same as >= and <= but it appears
that this is not the case.
Any ideas what would be causing this?
In both cases the statement was run from TCL when there select list
was exhausted.
Thanks
DTsig
If this is D3 check the MD entries for each on my system the GE and >=
have "cac" in attr 1 and the le entries have "cbc" in attribute 1.
On thing on you access statement...
It might be better to use: ....with chg_date ge "date" and le
"date"....
order.date order.dat
returned 1 of many items. The only one for the 17th
Oh my !!! i did edit it and it turns out that someone overwrote it
with a proc pointer <sigh>. Not sure why PICK didn't scream when it
tried to use it but at least now I know.
thanks .. i doubt i would have ever looked there
.
- Follow-Ups:
- Re: Odd Date selection
- From: Peter McMurray
- Re: Odd Date selection
- References:
- Odd Date selection
- From: dtsig
- Re: Odd Date selection
- From: Dale
- Odd Date selection
- Prev by Date: Re: Odd Date selection
- Next by Date: Re: FACTS
- Previous by thread: Re: Odd Date selection
- Next by thread: Re: Odd Date selection
- Index(es):