[ic] MORE-LIST blowing apart past page 1

[Barry Treahy, Jr.]

Mike Heins wrote:

>Quoting Barry Treahy, Jr. (Treahy@mmaz.com):
>  
>
>>Mike Heins wrote:
>>
>>    
>>
>>>Quoting Barry Treahy, Jr. (Treahy@mmaz.com):
>>> 
>>>
>>>      
>>>
>>>>I thought I was proceeding pretty well until I found that my 
>>>>[more-list]'s were in fact not working...  The first page of the loop is 
>>>>presented just fine, but if you clink for page 2 or Next, it is as if 
>>>>there were no search qualifies provided which were successfully applied 
>>>>for Page 1...
>>>>
>>>>An example of the complete loop in below, the 'more=1' was a recent 
>>>>addition after searching the archives, but that changed nothing.  In the 
>>>>case example I'm working with the following CGI values exist from the 
>>>>prior pages form and the scratch values were also processes and populated:
>>>>
>>>>BODY = 4HL
>>>>GENDERS = F
>>>>INTERFACES = SMA
>>>>CONTACT = undefined
>>>>
>>>>Any thoughts?
>>>>
>>>>Barry
>>>>
>>>>[loop
>>>>       prefix=CON
>>>>   
>>>>
>>>>        
>>>>
>>>Where is your more=1?
>>>
>>> 
>>>
>>>      
>>>
>>Hi Mike,
>>
>>it was in the original post:
>>    
>>
>
>Nope. You need [loop more=1 ...], not in the search.
>  
>
That was the final piece...  I sincerely appreciate the extra set of 
eyes as when I reviewed the docs, I saw in the examples that they 
followed the SQL statements wasn't paying close attention to the fact 
that the query had already been closed quoted.

Perhaps this is a silly questions, but wouldn't it make more sense for 
more=1 to be the default and then to let folks disable it?  

What is the benefit of running without more=1???  presuming that you 
could essentially make any list excessively large with the ml?

Regards,

Barry

-- 

Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIO 

E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028