Re: [WebDNA] Quick sort/results grouping Q

This WebDNA talk-list message is from

2008


It keeps the original formatting.
numero = 101369
interpreted = N
texte = --=====================_821379656==.ALT Content-Type: text/plain; charset="us-ascii" Thanks Pat! However I was looking for it to return just one [T_AREA] per [J_UNIT] and that was only if it shared common [T_AREAS] (so in database, they should both find that they have Warbler Village in common and list just that for the 109-2 and 109-3 J_UNIT's). I did manage to get it sorted out last night, but thanks! Gary At 10:22 AM 11/7/2008, you wrote: >I set it up with a tst.db that had this in it (to act like your table): >------------------------------------- >J_UNITIN_AREAT_AREA >109-2 ARTFunami DaiWestern Village >109-2 ARTFunami DaiWarbler Village >109-3 ARTChidori AirfieldWarbler Village >109-3 ARTChidori AirfieldDouble Root Beach >109-3 ARTChidori AirfieldWestern Coast >-------------------------------------- > > >Then I did this in the page: > >[search db=tst.db&neJ_UNITdatarq=[blank]&J_UNITsort=1&J_UNITsumm=T][founditems] >[J_UNIT] in [IN_AREA] has:
>[search db=tst.db&neJ_UNITdatarq=[J_UNIT]&asT_AREAsort=1][founditems] >   [T_AREA] in range.
>[/founditems][/search] >[/founditems][/search] > > > >Which produced this output: > >109-2 ART in Funami Dai has: > Double Root Beach in range. > Warbler Village in range. > Western Coast in range. >109-3 ART in Chidori Airfield has: > Warbler Village in range. > Western Village in range. > > > >On Nov 7, 2008, at 12:03 AM, Gary Krockover wrote: > >>If I have this query: >> >>[search table=LONGRANGE&neJ_UNITdatarq=[blank]&asT_AREAsort=1] >>[founditems] >>[J_UNIT] in [IN_AREA] has [T_AREA] in range.
>>[/founditems] >>[/search] >> >>That produces this result: >> >>109-2 ART in Funami Dai has Western Village in range. >>109-2 ART in Funami Dai has Warbler Village in range. >>109-3 ART in Chidori Airfield has Warbler Village in range. >>109-3 ART in Chidori Airfield has Double Root Beach in range. >>109-3 ART in Chidori Airfield has Western Coast in range. >> >>How can I group it so that [J_UNIT] (ex: 109-2 ART) appears only once and has the same T_AREA (ex: Funami Dai) as another T_UNIT? >> >>Optimal results would be: >> >>109-2 ART in Funami Dai has Warbler Village in range. >>109-3 ART in Chidori Airfield has Warbler Village in range. >> >>Possible without several nested searches possibly? >> >>GJK --=====================_821379656==.ALT Content-Type: text/html; charset="us-ascii" Thanks Pat!  However I was looking for it to return just one [T_AREA] per [J_UNIT] and that was only if it shared common [T_AREAS] (so in database, they should both find that they have Warbler Village in common and list just that for the 109-2 and 109-3 J_UNIT's).  I did manage to get it sorted out last night, but thanks!

Gary

At 10:22 AM 11/7/2008, you wrote:
I set it up with a tst.db that had this in it (to act like your table):
-------------------------------------
J_UNITIN_AREAT_AREA
109-2 ARTFunami DaiWestern Village
109-2 ARTFunami DaiWarbler Village
109-3 ARTChidori AirfieldWarbler Village
109-3 ARTChidori AirfieldDouble Root Beach
109-3 ARTChidori AirfieldWestern Coast
--------------------------------------


Then I did this in the page:

[search db=tst.db&neJ_UNITdatarq=[blank]&J_UNITsort=1&J_UNITsumm=T][founditems]
[J_UNIT] in [IN_AREA] has:<br>
[search db=tst.db&neJ_UNITdatarq=[J_UNIT]&asT_AREAsort=1][founditems]
&nbsp;&nbsp;&nbsp;[T_AREA] in range.<br>
[/founditems][/search]
[/founditems][/search]



Which produced this output:

109-2 ART in Funami Dai has:
   Double Root Beach in range.
   Warbler Village in range.
   Western Coast in range.
109-3 ART in Chidori Airfield has:
   Warbler Village in range.
   Western Village in range.



On Nov 7, 2008, at 12:03 AM, Gary Krockover wrote:

If I have this query:

[search table=LONGRANGE&neJ_UNITdatarq=[blank]&asT_AREAsort=1]
[founditems]
[J_UNIT] in [IN_AREA] has [T_AREA] in range.<br>
[/founditems]
[/search]

That produces this result:

109-2 ART in Funami Dai has Western Village in range.
109-2 ART in Funami Dai has Warbler Village in range.
109-3 ART in Chidori Airfield has Warbler Village in range.
109-3 ART in Chidori Airfield has Double Root Beach in range.
109-3 ART in Chidori Airfield has Western Coast in range.

How can I group it so that [J_UNIT] (ex: 109-2 ART) appears only once and has the same T_AREA (ex: Funami Dai) as another T_UNIT?

Optimal results would be:

109-2 ART in Funami Dai has Warbler Village in range.
109-3 ART in Chidori Airfield has Warbler Village in range.

Possible without several nested searches possibly?

GJK
--=====================_821379656==.ALT-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Quick sort/results grouping Q (Patrick McCormick 2008)
  2. Re: [WebDNA] Quick sort/results grouping Q (Gary Krockover 2008)
  3. Re: [WebDNA] Quick sort/results grouping Q (Patrick McCormick 2008)
  4. Re: [WebDNA] Quick sort/results grouping Q (Patrick McCormick 2008)
  5. Re: [WebDNA] Quick sort/results grouping Q (Patrick McCormick 2008)
  6. Re: [WebDNA] Quick sort/results grouping Q (Kenneth Grome 2008)
  7. Re: [WebDNA] Quick sort/results grouping Q (Gary Krockover 2008)
  8. Re: [WebDNA] Quick sort/results grouping Q (Stuart Tremain 2008)
  9. [WebDNA] Quick sort/results grouping Q (Gary Krockover 2008)
--=====================_821379656==.ALT Content-Type: text/plain; charset="us-ascii" Thanks Pat! However I was looking for it to return just one [T_AREA] per [J_UNIT] and that was only if it shared common [T_AREAS] (so in database, they should both find that they have Warbler Village in common and list just that for the 109-2 and 109-3 J_UNIT's). I did manage to get it sorted out last night, but thanks! Gary At 10:22 AM 11/7/2008, you wrote: >I set it up with a tst.db that had this in it (to act like your table): >------------------------------------- >J_UNITIN_AREAT_AREA >109-2 ARTFunami DaiWestern Village >109-2 ARTFunami DaiWarbler Village >109-3 ARTChidori AirfieldWarbler Village >109-3 ARTChidori AirfieldDouble Root Beach >109-3 ARTChidori AirfieldWestern Coast >-------------------------------------- > > >Then I did this in the page: > >[search db=tst.db&neJ_UNITdatarq=[blank]&J_UNITsort=1&J_UNITsumm=T][founditems] >[J_UNIT] in [IN_AREA] has:
>[search db=tst.db&neJ_UNITdatarq=[J_UNIT]&asT_AREAsort=1][founditems] >   [T_AREA] in range.
>[/founditems][/search] >[/founditems][/search] > > > >Which produced this output: > >109-2 ART in Funami Dai has: > Double Root Beach in range. > Warbler Village in range. > Western Coast in range. >109-3 ART in Chidori Airfield has: > Warbler Village in range. > Western Village in range. > > > >On Nov 7, 2008, at 12:03 AM, Gary Krockover wrote: > >>If I have this query: >> >>[search table=LONGRANGE&neJ_UNITdatarq=[blank]&asT_AREAsort=1] >>[founditems] >>[J_UNIT] in [IN_AREA] has [T_AREA] in range.
>>[/founditems] >>[/search] >> >>That produces this result: >> >>109-2 ART in Funami Dai has Western Village in range. >>109-2 ART in Funami Dai has Warbler Village in range. >>109-3 ART in Chidori Airfield has Warbler Village in range. >>109-3 ART in Chidori Airfield has Double Root Beach in range. >>109-3 ART in Chidori Airfield has Western Coast in range. >> >>How can I group it so that [J_UNIT] (ex: 109-2 ART) appears only once and has the same T_AREA (ex: Funami Dai) as another T_UNIT? >> >>Optimal results would be: >> >>109-2 ART in Funami Dai has Warbler Village in range. >>109-3 ART in Chidori Airfield has Warbler Village in range. >> >>Possible without several nested searches possibly? >> >>GJK --=====================_821379656==.ALT Content-Type: text/html; charset="us-ascii" Thanks Pat!  However I was looking for it to return just one [T_AREA] per [J_UNIT] and that was only if it shared common [T_AREAS] (so in database, they should both find that they have Warbler Village in common and list just that for the 109-2 and 109-3 J_UNIT's).  I did manage to get it sorted out last night, but thanks!

Gary

At 10:22 AM 11/7/2008, you wrote:
I set it up with a tst.db that had this in it (to act like your table):
-------------------------------------
J_UNITIN_AREAT_AREA
109-2 ARTFunami DaiWestern Village
109-2 ARTFunami DaiWarbler Village
109-3 ARTChidori AirfieldWarbler Village
109-3 ARTChidori AirfieldDouble Root Beach
109-3 ARTChidori AirfieldWestern Coast
--------------------------------------


Then I did this in the page:

[search db=tst.db&neJ_UNITdatarq=[blank]&J_UNITsort=1&J_UNITsumm=T][founditems]
[J_UNIT] in [IN_AREA] has:<br>
[search db=tst.db&neJ_UNITdatarq=[J_UNIT]&asT_AREAsort=1][founditems]
&nbsp;&nbsp;&nbsp;[T_AREA] in range.<br>
[/founditems][/search]
[/founditems][/search]



Which produced this output:

109-2 ART in Funami Dai has:
   Double Root Beach in range.
   Warbler Village in range.
   Western Coast in range.
109-3 ART in Chidori Airfield has:
   Warbler Village in range.
   Western Village in range.



On Nov 7, 2008, at 12:03 AM, Gary Krockover wrote:

If I have this query:

[search table=LONGRANGE&neJ_UNITdatarq=[blank]&asT_AREAsort=1]
[founditems]
[J_UNIT] in [IN_AREA] has [T_AREA] in range.<br>
[/founditems]
[/search]

That produces this result:

109-2 ART in Funami Dai has Western Village in range.
109-2 ART in Funami Dai has Warbler Village in range.
109-3 ART in Chidori Airfield has Warbler Village in range.
109-3 ART in Chidori Airfield has Double Root Beach in range.
109-3 ART in Chidori Airfield has Western Coast in range.

How can I group it so that [J_UNIT] (ex: 109-2 ART) appears only once and has the same T_AREA (ex: Funami Dai) as another T_UNIT?

Optimal results would be:

109-2 ART in Funami Dai has Warbler Village in range.
109-3 ART in Chidori Airfield has Warbler Village in range.

Possible without several nested searches possibly?

GJK
--=====================_821379656==.ALT-- Gary Krockover

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

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...

Related Readings:

Thanks and Big News!!! (1997) Absolute path (2003) Online reference (1997) website pro trouble (1998) Multi-processor Mac info ... (1997) [WebDNA] WebDNA Alive! (2012) Encrypt/Decrypt (2007) remotely add + sign (1997) Trigger time setting (2002) International Orders (1998) japanese characters (1997) ShowNext for method=POST (1997) FileMaker and WebCat - .hdr OK Merge not OK (1999) WebCat2b12 Mac.acgi--[searchstring] bug (1997) Calculating multiple shipping... (1997) checking for [ and ] in form fields ... (1997) lookup problem (2000) Almost a there but..bye bye NetCloak (1997) [isfile] ? (1997) Card clearance, problems - solutions? (1997)