numero = 12011
interpreted = N
texte = Thanks for the thoughts Gary, though I don't think the range methodology will solve my problem. From my understanding of the rn/mr comparisons, I think I really need the le/ge comparisions to be required on both fields as they are now. This has been working successfully to date. Its just that I now want to automatically screen out outdated events and that screws up the works.And I do want to screen out all the outdated events regardless of what other search arguements the client uses. So a couple of ideas...A> Can I nest the search in order to do multiple greater thans on the same field (first search would be [date], second would be user-supplied??B> Is there a way to string together some math that would say something like restrict my returns to only those records that have an ending date of [date] or a user supplied date value - whichever is greater?-thanks -marty ---------------- Gary wrote: ----------------> >have you looked at online reference searching numbers > > rn > range: field contains two numbers separated by space, or + > > rnZipCodedata=92069+93090 finds all records whose ZipCode field is >numerically in the > range of 92069 - 93090 > mr > minimum range value: if no maximum then ge is used instead > xr > maximum range value: if no minimum than le is used instead > >if you tell it type=date then according to the docs the above should come >into play. Using the range. I think you might be wrong cause you have >both le and ge fighting each other and need to think mr and xr. > >The next question was they click on specify date range and leave the rest >of the fields blank or geintdatarq becomes the current date you get no >records. > >Maybe change your checkbox to a radio button and add another radio button >both with the same name, and different values. The options would be do you >want to specify a given date or use [date]. then use a showif button >value=specify and place between the showif value=rq> and then do another show if right below this that says showif >button value= date then would be is either they can choose one or the other, but never a mixture of >both. Because radio buttons of the same name can't be both on at once. >Now I might have totally misunderstood your problem. But from what I could >gleem out this was the first concept that came to mind. Remember concept >only. > > > > > >=============================================== >Gary Richter > PanaVise Products, Inc. > 7540 Colbert Dr. Reno, Nevada 89511 > Ph: 702.850.2900 Fx: 702.850.2929 > Email: grichter@panavise.com > http://www.panavise.com >===============================================
Associated Messages, from the most recent to the oldest:
Thanks for the thoughts Gary, though I don't think the range methodology will solve my problem. From my understanding of the rn/mr comparisons, I think I really need the le/ge comparisions to be required on both fields as they are now. This has been working successfully to date. Its just that I now want to automatically screen out outdated events and that screws up the works.And I do want to screen out all the outdated events regardless of what other search arguements the client uses. So a couple of ideas...A> Can I nest the search in order to do multiple greater thans on the same field (first search would be [date], second would be user-supplied??B> Is there a way to string together some math that would say something like restrict my returns to only those records that have an ending date of [date] or a user supplied date value - whichever is greater?-thanks -marty ---------------- Gary wrote: ----------------> >have you looked at online reference searching numbers > > rn > range: field contains two numbers separated by space, or + > > rnZipCodedata=92069+93090 finds all records whose ZipCode field is >numerically in the > range of 92069 - 93090 > mr > minimum range value: if no maximum then ge is used instead > xr > maximum range value: if no minimum than le is used instead > >if you tell it type=date then according to the docs the above should come >into play. Using the range. I think you might be wrong cause you have >both le and ge fighting each other and need to think mr and xr. > >The next question was they click on specify date range and leave the rest >of the fields blank or geintdatarq becomes the current date you get no >records. > >Maybe change your checkbox to a radio button and add another radio button >both with the same name, and different values. The options would be do you >want to specify a given date or use [date]. then use a showif button >value=specify and place between the showif value=rq> and then do another show if right below this that says showif >button value= date then would be is either they can choose one or the other, but never a mixture of >both. Because radio buttons of the same name can't be both on at once. >Now I might have totally misunderstood your problem. But from what I could >gleem out this was the first concept that came to mind. Remember concept >only. > > > > > >=============================================== >Gary Richter > PanaVise Products, Inc. > 7540 Colbert Dr. Reno, Nevada 89511 > Ph: 702.850.2900 Fx: 702.850.2929 > Email: grichter@panavise.com > http://www.panavise.com >===============================================
Marty Schmid
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...