Re: [WebDNA] Search on a database

This WebDNA talk-list message is from

2012


It keeps the original formatting.
numero = 108756
interpreted = N
texte = > Govinda, >=20 > 1. I would like to see all of the fields' values displayed because I = don't know who is responding to this survey, or when, or even the = answers to any of the questions I've asked. I'm not looking for a = certain value in each field, I'm looking for the values in general. >=20 > 2. I don't understand the function pipe character. >=20 > Lori Good.. now we'll get somewhere. 0.) A webdna "context" is composed of 3 parts: - the opening "tag" (e.g. "[search ...]"),=20 - the closing tag (e.g. "[/search]") - and the stuff in between those. 1.) when you search a db, what you put inside the opening [search ...] = (<--- in here) tag is what determines *which records will be found* by = the search. =20 BUT, In order to determine which part(s) of the found record(s) get = displayed on the page, then you focus on what is inside the = [founditems]...[/founditems] context. So in your case you want the [search] parameters (what is in here: = [search ...] (<--- in here)) to be very brief.. probably just comparing = against a single field... but you want to be sure to list all fieldnames = (in square brackets) inside the [founditems]...[/founditems] context, = which is nested inside the [search]...[/search] context, so that you can = see ALL the field values of any found records. 2.) The pipe character does not serve any function at all, in the = situation we are talking about. It is for display purposes only. You = can leave it off completely, or replace it with another character that = you like better (anything other than square brackets). The reason I said to put the pipe was just to remind you where the = square bracket was, before you removed it, when you (if you tried what I = suggested) copied your real full search context and pasted that copy = adjacent to (just before) your real full search context (with the = square brackets *removed* from the [search] and [founditems]). =20 play with everything.. and keep rattling off every little thing that you = do not get.. =20 -G= Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Search on a database (Govinda 2012)
  2. Re: [WebDNA] Search on a database (Lori Palmquist 2012)
  3. Re: [WebDNA] Search on a database (Govinda 2012)
  4. Re: [WebDNA] Search on a database (Lori Palmquist 2012)
  5. Re: [WebDNA] Search on a database (Govinda 2012)
  6. Re: [WebDNA] Search on a database (Lori Palmquist 2012)
  7. Re: [WebDNA] Search on a database (Govinda 2012)
  8. Re: [WebDNA] Search on a database (Lori Palmquist 2012)
  9. Re: [WebDNA] Search on a database (Govinda 2012)
  10. Re: [WebDNA] Search on a database (Lori Palmquist 2012)
  11. Re: [WebDNA] Search on a database (Govinda 2012)
  12. Re: [WebDNA] Search on a database (Govinda 2012)
  13. Re: [WebDNA] Search on a database (Lori Palmquist 2012)
  14. Re: [WebDNA] Search on a database (Govinda 2012)
  15. Re: [WebDNA] Search on a database (aaronmichaelmusic@gmail.com 2012)
  16. [WebDNA] Search on a database (Lori Palmquist 2012)
> Govinda, >=20 > 1. I would like to see all of the fields' values displayed because I = don't know who is responding to this survey, or when, or even the = answers to any of the questions I've asked. I'm not looking for a = certain value in each field, I'm looking for the values in general. >=20 > 2. I don't understand the function pipe character. >=20 > Lori Good.. now we'll get somewhere. 0.) A webdna "context" is composed of 3 parts: - the opening "tag" (e.g. "[search ...]"),=20 - the closing tag (e.g. "[/search]") - and the stuff in between those. 1.) when you search a db, what you put inside the opening [search ...] = (<--- in here) tag is what determines *which records will be found* by = the search. =20 BUT, In order to determine which part(s) of the found record(s) get = displayed on the page, then you focus on what is inside the = [founditems]...[/founditems] context. So in your case you want the [search] parameters (what is in here: = [search ...] (<--- in here)) to be very brief.. probably just comparing = against a single field... but you want to be sure to list all fieldnames = (in square brackets) inside the [founditems]...[/founditems] context, = which is nested inside the [search]...[/search] context, so that you can = see ALL the field values of any found records. 2.) The pipe character does not serve any function at all, in the = situation we are talking about. It is for display purposes only. You = can leave it off completely, or replace it with another character that = you like better (anything other than square brackets). The reason I said to put the pipe was just to remind you where the = square bracket was, before you removed it, when you (if you tried what I = suggested) copied your real full search context and pasted that copy = adjacent to (just before) your real full search context (with the = square brackets *removed* from the [search] and [founditems]). =20 play with everything.. and keep rattling off every little thing that you = do not get.. =20 -G= Govinda

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:

Re: (1998) OT - Public Upload Security (2002) Looping a variable name with [index] (1999) Who on the list is available for contract work? (2000) [WebDNA] maybe silly suggestion? [founditems] (2015) I'm new (2001) Postdata expired from cache (2004) WebCat 4.0.1 HTTP_REFERRER over 255 char bug (2000) Separate SSL Server (1997) [WebDNA] Http or Https (2009) webcatalog 3.0 upgrade (1998) Converting Aliases to Symbolic Links (2002) emailer settings and control questions (1997) t or f (1997) Sorting problem (1997) RE: completed orders database (1997) [isfile] ? (1997) Projects & Contractors (1997) PCS Frames (1997) Help Please WebDNA 6 Secure Forms Problem (2004)