Re: default value from Lookup (was Grant, please help me)
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 12610
interpreted = N
texte = >>Suppose I do a lookup and one of the first records in the database matches >>the lookup parameters. Does the lookup stop there, or does it continue down >>thru the whole database until it reaches the end? > >Lookup stops at the first match -- another reason it is faster.That's what I was hoping ... plus, I figured you would code it this way, since the lookup only has to match one record anyways ... so why bother to look any further once it's found a match? ... :)Good. I split the problem database and quadrupled the size of both 'halves' ... and while one of those 'halves' works fine, the other still fails. Therefore, it seems very much to be a bad record somewhere in the db. I will try to run it down by using sequential lookups to pinpoint the problem record(s).Thanks, Grant, for the help, I'll let you know what I find. I've been stymied by this problem because this is exactly the same db I've been using for months without a single problem ... so that's one reason I thought it was okay, but apparently it's not anymore ... :)Sincerely, Ken Grome WebDNA Solutions http://www.hui.net/dna/webdna.html
Associated Messages, from the most recent to the oldest:
>>Suppose I do a lookup and one of the first records in the database matches >>the lookup parameters. Does the lookup stop there, or does it continue down >>thru the whole database until it reaches the end? > >Lookup stops at the first match -- another reason it is faster.That's what I was hoping ... plus, I figured you would code it this way, since the lookup only has to match one record anyways ... so why bother to look any further once it's found a match? ... :)Good. I split the problem database and quadrupled the size of both 'halves' ... and while one of those 'halves' works fine, the other still fails. Therefore, it seems very much to be a bad record somewhere in the db. I will try to run it down by using sequential lookups to pinpoint the problem record(s).Thanks, Grant, for the help, I'll let you know what I find. I've been stymied by this problem because this is exactly the same db I've been using for months without a single problem ... so that's one reason I thought it was okay, but apparently it's not anymore ... :)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:
WebCat2b12 - nesting [tags] (1997)
Listserver problem (1997)
MOOOOOO (2000)
Pls Remove me from all Lists (1998)
multi-paragraph fields (1997)
Help needed! (SIMS recommendation) (1998)
HELP..Changing Price after adding to cart. (1999)
[WebDNA] 6.2 Monitor (2012)
Templates on Unix & CGI on Mac? (1997)
[OT] MS IE from H3LL (2008)
[WebDNA] MD5 encryption (2011)
WebMerchant 1.6 and SHTML (1997)
Missing contexts on NT (1997)
Feature Request (2003)
question: webmerchant connection (1997)
[WebDNA] Silly question (2009)
[addlineitems] display (1997)
Memory Error message (1998)
Verifying and adding new users (1997)
auto-stripping of spaces (1997)