Re: [LOOKUP]

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 11771
interpreted = N
texte = >>I can't get the [LOOKUP] tag to return anything other than NotFound text >>string. I'm referencing a database that has 2 fields (sku and description). >> >>I've spelled the field names correctly. I have the comment >>in the page. >> >>What's wrong?! >> >>[LOOKUP >>db=../DB/description.db&value=94215&lookInField=[sku]&returnField=[descript >>ion]& >>notFound=Sorry, there is no profile available for this item.] >> >>I'm using the WC plugin (f3).John's right, in most cases you don't want touse brackets around the field names in the lookup database ...... also, don't forget that lookup requires an exact - CASE SENSITIVE - match of the 'value' parameter. It's really FAST, but it's not as flexible as [search] because it requires an exact match ...Sincerely, Ken Grome ..... ken@iav.com http://usarea.net/home.html Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] [lookup] fails when using [url] to wrap a value for potential "&" char? (John Butler 2009)
  2. Re: [WebDNA] [lookup] fails when using [url] to wrap a value for (Donovan Brooke 2009)
  3. Re: [WebDNA] [lookup] fails when using [url] to wrap a value for potential "&" char? (John Butler 2009)
  4. Re: [WebDNA] [lookup] fails when using [url] to wrap a value for potential "&" char? (Brian Fries 2009)
  5. [WebDNA] [lookup] fails when using [url] to wrap a value for potential "&" char? (John Butler 2009)
  6. Feature request: [decrypt seed=xxxxx] from [lookup] ( WJ Starck 2005)
  7. Re: [lookup] [search] Issue ( "Kenneth Grome" 2005)
  8. Re: [lookup] [search] Issue ( Mark Derrick 2005)
  9. Re: [lookup] [search] Issue ( Brian Fries 2005)
  10. Re: [lookup] [search] Issue ( "Kenneth Grome" 2005)
  11. Re: [lookup] [search] Issue ( Mark Derrick 2005)
  12. Re: [lookup] [search] Issue ( devaulw@onebox.com 2005)
  13. Re: [lookup] [search] Issue ( Mark Derrick 2005)
  14. Re: [lookup] [search] Issue ( Donovan Brooke 2005)
  15. Re: [lookup] [search] Issue ( nitai@computeroil.com 2005)
  16. [lookup] [search] Issue ( Mark Derrick 2005)
  17. Re: [Lookup] improvment [feature request] ( Donovan Brooke 2004)
  18. Re: [Lookup] improvment [feature request] ( Brian Fries 2004)
  19. [Lookup] improvment [feature request] ( Donovan Brooke 2004)
  20. Re: [lookup] again... ( Tim Robinson 2003)
  21. Re: [lookup] again... *solved* ( "Dan Strong" 2003)
  22. Re: [lookup] again... ( "Dan Strong" 2003)
  23. Re: [lookup] again... ( Joe D'Andrea 2003)
  24. [lookup] again... ( "Dan Strong" 2003)
  25. Re: [lookup] speed sales pitch ( Kenneth Grome 2003)
  26. Re: [lookup] speed sales pitch ( John Hill 2003)
  27. Re: [lookup] speed sales pitch ( John Peacock 2003)
  28. Re: [lookup] speed sales pitch ( Brian Fries 2003)
  29. Re: [lookup] speed sales pitch ( "Dan Strong" 2003)
  30. Re: [lookup] speed sales pitch ( Kenneth Grome 2003)
  31. Re: [lookup] speed sales pitch ( "Dan Strong" 2003)
  32. Re: [lookup] speed sales pitch ( Kenneth Grome 2003)
  33. Re: [lookup] speed sales pitch ( "Dan Strong" 2003)
  34. Re: [lookup] speed sales pitch ( John Peacock 2003)
  35. Re: [lookup] speed sales pitch ( "Dan Strong" 2003)
  36. Re: [lookup] speed sales pitch ( "Dan Strong" 2003)
  37. Re: [lookup] speed sales pitch ( Donovan Brooke 2003)
  38. Re: [lookup] speed sales pitch ( John Peacock 2003)
  39. [lookup] speed sales pitch ( "Dan Strong" 2003)
  40. Re: [lookup] is case-sensitive, [lookup] is case sensitive... (Dan Strong 2003)
  41. Re: [lookup] is case-sensitive, [lookup] is case sensitive... (Kenneth Grome 2003)
  42. Re: [lookup] is case-sensitive, [lookup] is case sensitive... (Dan Strong 2003)
  43. Re: [lookup] is case-sensitive, [lookup] is case sensitive... (WebCat @ Inkblot Media 2003)
  44. Re: [lookup] is case-sensitive, [lookup] is case sensitive... (WJ Starck 2003)
  45. Re: [lookup] is case-sensitive, [lookup] is case sensitive... (Dan Strong 2003)
  46. [lookup] is case-sensitive, [lookup] is case sensitive... (Dan Strong 2003)
  47. Re: Why is [lookup] case sensitive? (Charles Kline 2001)
  48. Why is [lookup] case sensitive? (Paul Uttermohlen 2001)
  49. Re: [Lookup] on secure page not returning anything (John Butler 2000)
  50. Re: [Lookup] on secure page not returning anything (John Butler 2000)
  51. Re: [Lookup] on secure page not returning anything (Michael O Shea 2000)
  52. [Lookup] on secure page not returning anything (John Butler 2000)
  53. Re: [LookUp] (charles kline 1999)
  54. Re: [LookUp] (charles kline 1999)
  55. Re: [LookUp] (Kenneth Grome 1999)
  56. More on [lookup] (charles kline 1999)
  57. [LookUp] (charles kline 1999)
  58. Re: return two fields w/ [lookup] (Peter Ostry 1998)
  59. Re: return two fields w/ [lookup] (PCS Technical Support 1998)
  60. Re: return two fields w/ [lookup] (Kenneth Grome 1998)
  61. return two fields w/ [lookup] (Charlie Romero 1998)
  62. Re: [lookup] still not working (Bob Minor 1998)
  63. [lookup] still not working (Mike Eberly 1998)
  64. RE: High ASCII inside [LOOKUP] inside [LISTWORDS] (Olin 1998)
  65. Re: High ASCII inside [LOOKUP] inside [LISTWORDS] (Michael Winston 1998)
  66. Re: High ASCII inside [LOOKUP] inside [LISTWORDS] (Michael Winston 1998)
  67. Re: High ASCII inside [LOOKUP] inside [LISTWORDS] (Gary Richter 1998)
  68. High ASCII inside [LOOKUP] inside [LISTWORDS] (Michael Winston 1998)
  69. Re: [lookup] vs. [search] (Kenneth Grome 1998)
  70. Re: [lookup] vs. [search] (Grant Hulbert 1998)
  71. [lookup] vs. [search] (Kenneth Grome 1998)
  72. Re: [LOOKUP] (Kenneth Grome 1997)
  73. [LOOKUP] (Michael Winston 1997)
  74. Re: [LOOKUP] (John Hill 1997)
  75. Re: [LOOKUP] (grichter@panavise.com (Gary Richter) 1997)
  76. Re: [LOOKUP] (Grant Hulbert 1997)
  77. Re: [LOOKUP] (John Hill 1997)
  78. [LOOKUP] (Christer Olsson 1997)
  79. [lookup] ( )
>>I can't get the [lookup] tag to return anything other than NotFound text >>string. I'm referencing a database that has 2 fields (sku and description). >> >>I've spelled the field names correctly. I have the comment >>in the page. >> >>What's wrong?! >> >>[LOOKUP >>db=../DB/description.db&value=94215&lookInField=[sku]&returnField=[descript >>ion]& >>notFound=Sorry, there is no profile available for this item.] >> >>I'm using the WC plugin (f3).John's right, in most cases you don't want touse brackets around the field names in the lookup database ...... also, don't forget that lookup requires an exact - CASE SENSITIVE - match of the 'value' parameter. It's really FAST, but it's not as flexible as [search] because it requires an exact match ...Sincerely, Ken Grome ..... ken@iav.com http://usarea.net/home.html Kenneth Grome

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: How can I record purchases to a database? (1998) default error on NT? (1997) A quickie question (1997) Simple way to create unique SKU (1997) [HIDEIF] inside [FOUNDITEM] (1997) possible, WebCat2.0 and checkboxes-restated (1997) creating a ShipCosts database (1997) Access Denied! But why? (1997) [WebDNA] How to build a Ubuntu 18.04 server on DigitalOcean (2019) Duplicate Carts (2000) [shipTotal] or [shippingTotal] ??? (1998) Is Typhoon 4 or Typhoon Pro a product? (2000) Bug or syntax error on my part? (1997) _ in front of field name (1998) checkout.tpl (1999) [urgent] Phone number at SM (2006) FEW QUESTIONS (1997) [append] vs. [appendfile] delta + question? (1997) RE: problems with dos and tracert + webDNA (1998) Testing (2003)