Re: default value from Lookup (was Grant, please help me)

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 12599
interpreted = N
texte = >>Do you know of anything in the WebCat2 code that will fail when the lookup >>database gets to a certain size or a certain number of records? I cannot >>think of anything else that could be causing this problem ... > >No, there are no inherent limits. Can you try switching to a [search] >instead, just to see what records appear when using search instead of >lookup? You can get almost the same speed as [lookup] if you turn case >sensitivity on, and use eq for exact matching.In all my testing to date, I have had some WebDNA code displayed on the page to show me what username/password values are being used by WebCat2 to authenticate the page. This technique makes it easy for me to see what's going on.I did what you recommended with [search], but no matching records are being displayed. It behaves just loke the [lookup] did ... with the large database.Sincerely, Ken Grome WebDNA Solutions http://www.hui.net/dna/webdna.html Associated Messages, from the most recent to the oldest:

    
  1. Re: default value from Lookup (was Grant, please help me) (Kenneth Grome 1997)
  2. Re: default value from Lookup (was Grant, please help me) (Grant Hulbert 1997)
  3. Re: default value from Lookup (was Grant, please help me) (Kenneth Grome 1997)
  4. Re: default value from Lookup (was Grant, please help me) (Grant Hulbert 1997)
  5. Re: default value from Lookup (was Grant, please help me) (Kenneth Grome 1997)
  6. Re: default value from Lookup (was Grant, please help me) (Grant Hulbert 1997)
  7. Re: default value from Lookup (was Grant, please help me) (Kenneth Grome 1997)
  8. Re: default value from Lookup (was Grant, please help me) (Grant Hulbert 1997)
>>Do you know of anything in the WebCat2 code that will fail when the lookup >>database gets to a certain size or a certain number of records? I cannot >>think of anything else that could be causing this problem ... > >No, there are no inherent limits. Can you try switching to a [search] >instead, just to see what records appear when using search instead of >lookup? You can get almost the same speed as [lookup] if you turn case >sensitivity on, and use eq for exact matching.In all my testing to date, I have had some WebDNA code displayed on the page to show me what username/password values are being used by WebCat2 to authenticate the page. This technique makes it easy for me to see what's going on.I did what you recommended with [search], but no matching records are being displayed. It behaves just loke the [lookup] did ... with the large database.Sincerely, Ken Grome WebDNA Solutions http://www.hui.net/dna/webdna.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:

[WebDNA] XML error? (2015) Ampersand (1997) Variables for chat (1997) Webcatalog error, Plug-in for Webstar (1996) [taxrate] question (1997) (1997) multi-paragraph fields (1997) X Server (1999) NetCloak as Emailer substitute? (1999) [WebDNA] BBEdit Codeless Language Module for WebDNA (2009) append/replace and allcase=t (sorry) (2000) WebCatb15 Mac CGI -- [purchase] (1997) [isfile] ? (1997) ODBC Performance? (2001) [ShowNext] feature in 2.0 (1997) Not really WebCat (1997) [WebDNA] Lookup vs. Search (2009) WebDNA maxing out processor (2008) formula inside database to calculate weights (1997) WebDNA deletes major DB data big time (2004)