Re: Help need to figure this out today!!! Advanced Question
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 59816
interpreted = N
texte = I followed the whole thread, and I'm recommending a simpler approach. I come up against this frequently, and I do it by summing and sorting on the (in your case) neighborhood name, in the listings.db, bypassing the hood.db altogether. You will have to add a neighborhood name field to your listings DB, or make that your matching record instead of the hoodID (which is probably not what you want to display). If the neighborhood name in the hood.db changes, it's not a problem to perform a second [replace] on the listings.db to update the affected records. This occasional extra processing is cleaner and much simpler than extraordinary measures, even using [table], which is somewhat clean, to achieve what you want. I have a situation just like this at http://sjyardsales.com in the top right popup menu of towns with yard sales (and again at the bottom for check boxes). It only shows selections for towns that actually have something in the founditems, something you are also trying to do. Yes, it's redundancy, but not such a bad thing. It gives you another piece of data to play with if you need it, without having to look it up from the other DB. Less is more. Terry >PROBLEM: I have 2 related databases: 1 a listing of businesses (listings.db) >and 2 a list of neighborhoods (hoods.db). They are related by HoodID being ------------------------------------------------------------- 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:
I followed the whole thread, and I'm recommending a simpler approach. I come up against this frequently, and I do it by summing and sorting on the (in your case) neighborhood name, in the listings.db, bypassing the hood.db altogether. You will have to add a neighborhood name field to your listings DB, or make that your matching record instead of the hoodID (which is probably not what you want to display). If the neighborhood name in the hood.db changes, it's not a problem to perform a second [replace] on the listings.db to update the affected records. This occasional extra processing is cleaner and much simpler than extraordinary measures, even using [table], which is somewhat clean, to achieve what you want. I have a situation just like this at http://sjyardsales.com in the top right popup menu of towns with yard sales (and again at the bottom for check boxes). It only shows selections for towns that actually have something in the founditems, something you are also trying to do. Yes, it's redundancy, but not such a bad thing. It gives you another piece of data to play with if you need it, without having to look it up from the other DB. Less is more. Terry >PROBLEM: I have 2 related databases: 1 a listing of businesses (listings.db) >and 2 a list of neighborhoods (hoods.db). They are related by HoodID being ------------------------------------------------------------- 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/
Terry Wilson
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:
multiple search commands (1997)
quotation marks needed? (2000)
Re1000001: Setting up shop (1997)
Windows 2000 Server & Webcatalog 3.x (2000)
The beginning (1997)
ftp ng (1999)
Bug or syntax error on my part? (1997)
Showif Error Generated... (2003)
SKU (1997)
Applescript error (1998)
[WebDNA] [OT] WebDNA Wiki - need grammar check / suggestions (2009)
If Empty ? (1997)
Not really WebCat (1997)
[WebDNA] IF statement evaluation bug report, WebDNA 8.5.1 (2019)
Non-Cart Files in Shopping Cart Folder (1997)
multi-paragraph fields (1997)
Sku numbers (1997)
Text Variabels Not Passed To Include (2002)
First Attempts (2000)
[WebDNA] MD5 Hash issue (2009)