Do While Loop nested in another While causes error

Re: Do While Loop nested in another While causes error

Thanks for your help

I considered the "Run out of records" problem, but the error comes before
any of the data is written, not at the end.
O well....onto a GROUP solution.

Mal.


"Mike Brind" wrote in message
news:usFfxulCHHA.1300@TK2MSFTNGP03.phx.gbl...
> Oh I see know. In which case, the approach I offered in my last post is
> definitely the way to go. Try to avoid nested loops wherever possible.
>
> If, as an exercise, you want to debug the nested loop, try the
> response.write suggestion. If you use On Error Resume Next to suppress
> error mesages, set the server.scripttimeout to 10 or so. This will stop
> any infinite loops from going on too long. Error 80020009 usually
> suggests you have run out of records.
>
> --
> Mike Brind
>
>
> "Mal Reeve" wrote in message
> news:r5k7h.7718$L6.4352@newsread3.news.pas.earthlink.net...
>> The WHY is because the query contains (and is searchable) on the Year for
>> an Alumni.
>> (from a one to many join). My access query Concats this info into one
>> field to display.
>> Eg.
>> Mike Smith
>> Years: 2001, 2002, 2003
>>
>> rather than having 3 listings for him - hence not possible for DISTINCT,
>> but very doable with GROUP.
>>
>> HOWEVER...
>>
>> still doesn't explain why a nested DO loop would cause problems.
>>
>> Thanks for your help,
>> Mal.
>>
>>
>> "Mike Brind" wrote in message
>> news:%23hXDSIlCHHA.5012@TK2MSFTNGP06.phx.gbl...
>>>I can see what you are trying to do - I'm just a bit bemused as to why.
>>>Do all the fields come from the same table? Your field names suggest
>>>they do. If so, why do you have repeating IDs in there?
>>>
>>> Until you sort out the contents of the recordset, get rid of your nested
>>> loops and try it like this instead:
>>>
>>> idHolder = ""
>>> Do While Not rsGuestbook.EOF
>>> If rsGuestbook("tblAlumniID") <> idHolder Then Response.Write stuff
>>> idHolder = rsGuestbook("tblAlumniID")
>>> rsGuestbook.Movenext
>>> Loop
>>>
>>>
>>> --
>>> Mike Brind
>>>
>>>
>>> "Mal Reeve" wrote in message
>>> news:E0j7h.7691$l25.7681@newsread4.news.pas.earthlink.net...
>>>> My logic tells me that I don't need an outer movenext
>>>> Initially the ID's are the same, so the inner loop does the movenext
>>>> eventually it "move'snext" then compares and finds that they are now
>>>> different,
>>>> in which case it moves back to the outer loop...and cycles again to
>>>> display that new ID.
>>>>
>>>> That being said, thanks for the write advice...
>>>> And although I can't use a DISTINCT due to some differing data (year
>>>> specific), I had not even thought about GROUP...and will explore that.
>>>>
>>>> Mal.
>>>>
>>>>
>>>> "Mike Brind" wrote in message
>>>> news:eMVwZukCHHA.3916@TK2MSFTNGP06.phx.gbl...
>>>>> You are still missing a movenext for the outer loop. Also,
>>>>> response.Write the value of idHolder within the loop(s) to see if it
>>>>> is what you expect.
>>>>>
>>>>> Having said that, why are you trying to cycle through rows until the
>>>>> ID changes? Why not change the SQL statement to only select unique
>>>>> tblAlumniID's using GROUP BY Or DISTINCT?
>>>>>
>>>>> --
>>>>> Mike Brind
>>>>>
>>>>>
>>>>> "Mal Reeve" wrote in message
>>>>> news:w8i7h.7247$0r.971@newsread1.news.pas.earthlink.net...
>>>>>>I was summarizing the code...sorry.
>>>>>> Here is the applicable loops in question, thanks for any advice.
>>>>>>
>>>>>> Mal.
>>>>>> -----------------------------------------------
>>>>>> 'This code follows other page elements.
>>>>>> ' Error occurs at second DO loop
>>>>>>
>>>>>>
>>>>>> rsGuestbook.Open strSQL, adoCon
>>>>>>
>>>>>> Response.Write("