>>>>>>>>>>I'll help Nick, George. I'm a dark beer drinker myself (well, that and tequila).
>>>>>>>>>>
>>>>>>>>>Hi Bonnie,
>>>>>>>>>
>>>>>>>>>Just have one for me, guys. I'll be thinking about ya.:-)
>>>>>>>>
>>>>>>>>.... or two, or three, or .... :-)
>>>>>>>
>>>>>>>One tequila, two tequila, three tequila, floor! ;)
>>>>>>
>>>>>>Ah, Fred, you floor me. Or is that =FLOOR(lnTequilas)< g >.
>>>>>
>>>>>No, the following code example should be correct, assuming you've previously instantiated the Fred object:
>>>>>
>>>>>

DO WHILE Fred.drinks.count < 3
>>>>>   oJustOneMore = NEWOBJECT('Tequila.shot')
>>>>>   Fred.drinks.add(oJustOneMore)
>>>>>   oJustOneMore = NULL
>>>>>ENDDO
>>>>>SEEK floor
>>>>>

>>>>
>>>>It's not like you to forget something
>>>>

DO WHILE Fred.drinks.count < 3
>>>>   oJustOneMore = NEWOBJECT('Tequila.shot')
>>>>   Fred.drinks.add(oJustOneMore)
>>>>   oJustOneMore = NULL
>>>>ENDDO
>>>>BROWSE BUUIICKK
>>>>SEEK floor
>>>>

>>>>
>>>>Jeff
>>>
>>>Are you guys sure you need that oJustOneMore = NULL line? Then again, I use NEWOBJECT() to create a reference to a 'Beer.Can' object, so I'm not familar with this. Of course, after a number of iterations, I have to call the GoToCan method.:-)
>>
>>
>>George
>>
>>But Real.Dark.Beer can not be contained in a Beer.Can object due to reactions with the environment, it must be kept in Heavy.Dark.Glass.Bottles |-).
>
>This is true. It's just that I rarely get a Real.Dark.Beer so more often than not it is in a Beer.Can object < sigh >.

Yes I see your point, obtaining a pint o'stout can be problematic in smallish Southern US towns like we live in.