![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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 |
#3
| |||
| |||
|
|
On Mar 26, 11:51 am, "dtsig" <d... (AT) hotmail (DOT) com> wrote: 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".... sort invoices with order.date GE "03-14-07" and LE "03-17-07" by-dsnd |
#4
| |||
| |||
|
|
On Mar 26, 12:42 pm, "Dale" <dale_bened... (AT) flightcraft (DOT) ca> wrote: On Mar 26, 11:51 am, "dtsig" <d... (AT) hotmail (DOT) com> wrote: 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".... sort invoices with order.date GE "03-14-07" and LE "03-17-07" by-dsnd 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 |
#5
| |||
| |||
|
|
Hi You certainly have some dingbats around. I have had to remove ED from at least one site in the past but I suppose this LuLu could have been done by a programmer with less intellectual ability than is normally associated with the job. I look forward to your future announcements of alternative programming approaches. It does one good to hear that one is not alone. Peter McMurray "dtsig" <dtsig (AT) hotmail (DOT) com> wrote in message news:1174939189.283735.148940 (AT) y80g2000hsf (DOT) googlegroups.com... On Mar 26, 12:42 pm, "Dale" <dale_bened... (AT) flightcraft (DOT) ca> wrote: On Mar 26, 11:51 am, "dtsig" <d... (AT) hotmail (DOT) com> wrote: 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".... sort invoices with order.date GE "03-14-07" and LE "03-17-07" by-dsnd 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 |
#6
| |||
| |||
|
|
On a related subject, does this syntax not work on any Pick (or jbase) system: SELECT file dictword1 dictword2 ... where the select list will have pairs (in this case) of selected data? I use this a lot. Chandru |
#7
| |||
| |||
|
|
On Mar 27, 6:45 am, "Chandru Murthi" cmur_xyz_thi (AT) xyz_seeinggree_xyz_n (DOT) net> wrote: On a related subject, does this syntax not work on any Pick (or jbase) system: SELECT file dictword1 dictword2 ... where the select list will have pairs (in this case) of selected data? I use this a lot. Chandru Chandru... This style of select works well on D3. I use it a lot. A few things to be wary of... 1. You really don't get 'pairs' of data if you are working with multi- valued attributes. Each multi-value takes an attribute in the select list generated. Sort by-exp really helps here! 2. Donno about other system, but each piece of data retrieved from the file will create an attribute in the select list. 'Pairing' the data when read from the select list technically does not happen. The pairing is really done by the programmer who realizes that two readnexts are required to get the paired set of data (In your case). hth Dale |
#8
| |||
| |||
|
|
On Mar 27, 3:12 am, "Peter McMurray" <excalibu... (AT) bigpond (DOT) com> wrote: Hi You certainly have some dingbats around. I have had to remove ED from at least one site in the past but I suppose this LuLu could have been done by a programmer with less intellectual ability than is normally associated with the job. I look forward to your future announcements of alternative programming approaches. It does one good to hear that one is not alone. I worked at one site where the md entry for NE had been overwritten, because of a pseudo login for the north east branch... sigh |
![]() |
| Thread Tools | |
| Display Modes | |
| |