Re: Looping Search
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 66763
interpreted = N
texte = 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 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:
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 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:
Date Sorting (1997)
[OT] Mac Utility Required (2000)
Thanks Grant (1997)
process SSI (1998)
Newbie Tax Question (1997)
[WebDNA] [announce] WebDNA Site and Store (2008)
type 2 errors with ssl server (1997)
RE: [shownext] support - MacOS (1997)
Searchable list archive (1997)
WebCat2b13MacPlugIn - [shownext method=post] ??? (1997)
Anyone with a solution for this? (2001)
Formatting a .txt file (1998)
PCS Customer submissions ? (1997)
[WebDNA] users.db (2009)
[include file=filename.inc&strip=t] (2002)
[WebDNA] ubuntu can't append db (2019)
Searching multiple fields from one form field (1997)
Mozilla/4. and Browser Info.txt (1997)
Initiating NewCart (1997)
Sending order notification by fax (1999)