Re: Looping Search

This WebDNA talk-list message is from

2006


It keeps the original formatting.
numero = 66765
interpreted = N
texte = I *do* have a field in the database where each person's immediate supervisor is listed. Right now, Person 1 is hard coded into the page. A [search] for anyone whose immediate supervisor is Person 1 yields the Person 2 listing and so on down the chain. This works unless someone at the top is removed: if Person 2 left, Persons 3, 8, and 11 would have to be reassigned to Person 1 as their immediate supervisor, or the whole chart would break. On 4/5/06 2:57 PM, "Pat McCormick" wrote: > Why not just have a field for immediate supervisor for every Person? > A demotion simply means changing the supervisor field. Or i guess it > could also mean coming to a stop. (get it? demotion? anyone?) > > > 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 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)
I *do* have a field in the database where each person's immediate supervisor is listed. Right now, Person 1 is hard coded into the page. A [search] for anyone whose immediate supervisor is Person 1 yields the Person 2 listing and so on down the chain. This works unless someone at the top is removed: if Person 2 left, Persons 3, 8, and 11 would have to be reassigned to Person 1 as their immediate supervisor, or the whole chart would break. On 4/5/06 2:57 PM, "Pat McCormick" wrote: > Why not just have a field for immediate supervisor for every Person? > A demotion simply means changing the supervisor field. Or i guess it > could also mean coming to a stop. (get it? demotion? anyone?) > > > 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 Web Archive of this list is at: http://webdna.smithmicro.com/ Clint Davis

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:

Need help with emailer- 2 issues (1997) Math, Multiple Equasions and Show/Hide (1998) webDNA on centos (2008) [NT] ie 4.0 required (1997) RAM variables (1997) Number searching/formats (1998) Need NT Assist. w/ Emailer (2000) Hiding URL ? (1998) RE: Emailer Timing out (1999) Problems searching from a FORM (1997) Database Structure? (1998) Non-Cart Files in Shopping Cart Folder (1997) Core Database integration (2001) Show shoppingcart after remove last item (1997) item sorting (1997) taxTotal (1997) problem: mail changed (1997) WebCat2b15MacPlugin - showing [math] (1997) Nested tags count question (1997) webcat NT with [dos] command (1997)