Re: REPLACE & MAX/STARTAT parameters doesn't work?
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 36405
interpreted = N
texte = >Someone at Smith Micro can correct me if I'm wrong, but since the >[replace] context does not use a [founditems]-like loop, the startat >and max parameters have no meaning. They are only useful if you are >looping through the found items. I hope this helps.No that's not right -- we expressly designed [replace] to follow exactly the same form as [search], for exactly this reason: we want you to be able to replace just the same record set that you could find in an equivalent search. So if [replace] doesn't appear to be following those rules, then there must be some other reason for it (perhaps it's nested inside some other context that's changing records before [replace] has a chance at them).-- Technical Support **********************************Smith Micro, Internet Solutions Div | eCommerce (WebCatalog)16855 West Bernardo Drive, #380 | -------------------------San Diego, CA 92127 | Software & Site DevelopmentWebCatalog Support: (858) 675-0632 | http://www.smithmicro.com Fax: (858) 675-0372 **********************************-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list
.To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>Someone at Smith Micro can correct me if I'm wrong, but since the >[replace] context does not use a [founditems]-like loop, the startat >and max parameters have no meaning. They are only useful if you are >looping through the found items. I hope this helps.No that's not right -- we expressly designed [replace] to follow exactly the same form as [search], for exactly this reason: we want you to be able to replace just the same record set that you could find in an equivalent search. So if [replace] doesn't appear to be following those rules, then there must be some other reason for it (perhaps it's nested inside some other context that's changing records before [replace] has a chance at them).-- Technical Support **********************************Smith Micro, Internet Solutions Div | eCommerce (WebCatalog)16855 West Bernardo Drive, #380 | -------------------------San Diego, CA 92127 | Software & Site DevelopmentWebCatalog Support: (858) 675-0632 | http://www.smithmicro.com Fax: (858) 675-0372 **********************************-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
WebDNA Support
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:
Date problems (1997)
[WebDNA] WebDNA future (2010)
[WebDNA] [text scope=global] (2014)
update on wn searching (1997)
Cookies and webcat (1997)
Error: Too many nested [xxx] contexts (1997)
Multiple prices (1997)
Reloading adds items - how to prevent?? (1998)
[CART] (1997)
Sami -pdf (1998)
Emailed problem (2000)
WebCatalog Hosting (1996)
[TaxableTotal] - not working with AOL and IE (1997)
Emailer setup (1997)
Re[2]: Enhancement Request for WebCatalog-NT (1996)
OFF-TOPIC: Lending investors ... (2002)
Sort Order on a page search (1997)
database size? (1997)
Lookup Notfound (1998)
help with writefile (1998)