numero = 14806
interpreted = N
texte = >At 04:15 PM 11/17/97, you wrote:>>>[search db=colors.db&eqSKUdata=[SKU]]>>>>>>>Let's simplify this a bit. If you're saying that>>>>[search db=colors.db&eqSKUdata=dg1900]>>[numFound]>>[/search]>>>>returns 0, then you've got problems that are unrelated to nested searching>-- the database fieldnames are messed up, or the data isn't there, or the>database is not formatted correctly.>>Wow, I actually just did the [numFound] thing about 10 min ago and got 0 so>I figured there was a problem with the fieldnames or database and was>working on that..>>Maby I am getting a little clue of how this works.>>Thank's!>>RayRay a simple tip when having search problems is show everything in the databaseie [search db=colors&neskudata=0] or use the new blank feature[numfound][/search]neskudata wil show every record in the color data base that does not equallzero.Then insert[founditems][fieldname1] <-where inside the [ ] is your field names[fieldname2] <-where inside the [ ] is your field namesetc.[/founditemsbetween the [search] [/search]Ie poor the data out on a page first and see what you have then startworking on tightening up the search to work the way you want it.As Grant says something could be wrong in the field names. I will admitthat I have mis-speeled a field name before and pulled my hair out tryingto figure out why the search didn't work. But pooring it all out proves itis there and working correctly. Example over the weekend the field mresetis not spelled mrset. That little e missing after the r messed me up for afew hours :)from a browser just load this page because you are using the [search][/search] tags.Keep in mind that the tag [search] starts the search and the [/search]tells it I am thru with this search and want to do something else, maybeanother search or link to another page, whateverIt is the [founditems] that starts the looping and the [/founditems] thattells it to go back to the upper [founditems] tag and get the next recordthat matches and then do what ever is between those two tags.Hope this helps===============================================Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com===============================================
Associated Messages, from the most recent to the oldest:
>At 04:15 PM 11/17/97, you wrote:>>>[search db=colors.db&eqSKUdata=[SKU]]>>>>>>>Let's simplify this a bit. If you're saying that>>>>[search db=colors.db&eqSKUdata=dg1900]>>[numFound]>>[/search]>>>>returns 0, then you've got problems that are unrelated to nested searching>-- the database fieldnames are messed up, or the data isn't there, or the>database is not formatted correctly.>>Wow, I actually just did the [numFound] thing about 10 min ago and got 0 so>I figured there was a problem with the fieldnames or database and was>working on that..>>Maby I am getting a little clue of how this works.>>Thank's!>>RayRay a simple tip when having search problems is show everything in the databaseie [search db=colors&neskudata=0] or use the new blank feature[numfound][/search]neskudata wil show every record in the color data base that does not equallzero.Then insert[founditems][fieldname1] <-where inside the [ ] is your field names[fieldname2] <-where inside the [ ] is your field namesetc.[/founditemsbetween the [search] [/search]Ie poor the data out on a page first and see what you have then startworking on tightening up the search to work the way you want it.As Grant says something could be wrong in the field names. I will admitthat I have mis-speeled a field name before and pulled my hair out tryingto figure out why the search didn't work. But pooring it all out proves itis there and working correctly. Example over the weekend the field mresetis not spelled mrset. That little e missing after the r messed me up for afew hours :)from a browser just load this page because you are using the [search][/search] tags.Keep in mind that the tag [search] starts the search and the [/search]tells it I am thru with this search and want to do something else, maybeanother search or link to another page, whateverIt is the [founditems] that starts the looping and the [/founditems] thattells it to go back to the upper [founditems] tag and get the next recordthat matches and then do what ever is between those two tags.Hope this helps===============================================Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com===============================================
grichter@panavise.com (Gary Richter)
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...