Re: Looping Search

This WebDNA talk-list message is from

2006


It keeps the original formatting.
numero = 66764
interpreted = N
texte = You would only have to set up a counter that increments every time a higher supervisor exists. Use a outer [loop] with the count equal to that counter result. On Apr 5, 2006, at 2:24 PM, Clint Davis wrote: > I need to setup and org chart like this: > > Person 1 > -----Person 2 > ----------Person 3 > ---------------Person 4 > ---------------Person 5 > ---------------Person 6 > ---------------Person 7 > ----------Person 8 > ---------------Person 9 > ---------------Person 10 > ----------Person 11 > ---------------Person 12 > ---------------Person 13 > ---------------Person 14 > > All of these people have a record in the personnel database with a > field for > their immediate supervisor. Can this be done with a [loop]'ed [search] > versus my current nested [search]es? I don't want it to break if > Person 3 > gets demoted, for example. > > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to digest@talk.smithmicro.com> > Web Archive of this list is at: http://webdna.smithmicro.com/ > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Ruby on Rails (was Looping Search) ( "Bess Ho" 2006)
  2. Re: Ruby on Rails (was Looping Search) ( Pat McCormick 2006)
  3. Re: Ruby on Rails (was Looping Search) ( Gary Krockover 2006)
  4. Re: Ruby on Rails (was Looping Search) ( devaulw@onebox.com 2006)
  5. Re: Ruby on Rails (was Looping Search) ( chas conquest 2006)
  6. Re: Ruby on Rails (was Looping Search) ( Pat McCormick 2006)
  7. Re: Ruby on Rails (was Looping Search) ( chas conquest 2006)
  8. Re: Ruby on Rails (was Looping Search) ( chas conquest 2006)
  9. Re: Ruby on Rails (was Looping Search) ( Pat McCormick 2006)
  10. Re: Ruby on Rails (was Looping Search) ( devaulw@onebox.com 2006)
  11. Re: Ruby on Rails (was Looping Search) ( Pat McCormick 2006)
  12. Re: Ruby on Rails (was Looping Search) ( devaulw@onebox.com 2006)
  13. Re: Ruby on Rails (was Looping Search) ( Brian Fries 2006)
  14. Re: Ruby on Rails (was Looping Search) ( Adam O'Connor 2006)
  15. Re: Ruby on Rails (was Looping Search) ( Gary Krockover 2006)
  16. Re: Ruby on Rails (was Looping Search) ( Adam O'Connor 2006)
  17. Re: Ruby on Rails (was Looping Search) ( chas conquest 2006)
  18. Re: Ruby on Rails (was Looping Search) ( nitai@computeroil.com 2006)
  19. Re: Ruby on Rails (was Looping Search) ( "Bess Ho" 2006)
  20. Re: Ruby on Rails (was Looping Search) ( nitai@computeroil.com 2006)
  21. Re: Ruby on Rails (was Looping Search) ( "Bess Ho" 2006)
  22. Re: Ruby on Rails (was Looping Search) ( j.list@blueboxdev.com 2006)
  23. Re: Ruby on Rails (was Looping Search) ( devaulw@onebox.com 2006)
  24. Re: Looping Search ( Alex McCombie 2006)
  25. Re: Ruby on Rails (was Looping Search) ( Clint Davis 2006)
  26. Re: Looping Search ( devaulw@onebox.com 2006)
  27. Re: Looping Search ( Alex McCombie 2006)
  28. Re: Looping Search ( Clint Davis 2006)
  29. Re: Looping Search ( devaulw@onebox.com 2006)
  30. Re: Looping Search ( Dale Lists 2006)
  31. Re: Looping Search ( Clint Davis 2006)
  32. Re: Looping Search ( Pat McCormick 2006)
  33. Re: Looping Search ( Pat McCormick 2006)
  34. Looping Search ( Clint Davis 2006)
  35. Re: Looping Search Results - Duh! (WebDNA Support 2000)
  36. Re: Looping Search Results - Duh! (Glenn Busbin 2000)
You would only have to set up a counter that increments every time a higher supervisor exists. Use a outer [loop] with the count equal to that counter result. On Apr 5, 2006, at 2:24 PM, Clint Davis wrote: > I need to setup and org chart like this: > > Person 1 > -----Person 2 > ----------Person 3 > ---------------Person 4 > ---------------Person 5 > ---------------Person 6 > ---------------Person 7 > ----------Person 8 > ---------------Person 9 > ---------------Person 10 > ----------Person 11 > ---------------Person 12 > ---------------Person 13 > ---------------Person 14 > > All of these people have a record in the personnel database with a > field for > their immediate supervisor. Can this be done with a [loop]'ed [search] > versus my current nested [search]es? I don't want it to break if > Person 3 > gets demoted, for example. > > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to digest@talk.smithmicro.com> > Web Archive of this list is at: http://webdna.smithmicro.com/ > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Pat McCormick

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:

taxTotal, grandTotal (1997) [WebDNA] Version 8 (2014) Fun with dates (1997) RE: Help name our technology! (1997) I'm having trouble using [url][interpret][math] together inlookup (1997) WebCat2b13MacPlugin - [math][date][/math] problem (1997) Searching for foreign chars (2004) BUG in [showif] using ^ (contains) (1997) Multiple prices (1997) Re:What file? (1997) SetHeader (1997) RE: ANother SHOWIF problem (1997) RE: AccountAuthorizer doesn't seem to work (1997) RE: Can a database get stomped by simultaneous access? (1997) NT error logs (1997) Setting up WebCatalog with Retail Pro data (1996) Pulldown Menu Problem (2000) credit card authorization question (1997) [purchase] question (2000) SetHeader not Working (2006)