On Mon, 21 Feb 2005 19:03:56 -0500, Andrew Rosborough
<[email protected]> wrote:
> l.completeorder looks like “Pizza,Large
White,,1;Subs,Cheesesteak,,1;Subs,Cheesesteak with Works,Sauce, Lettuce
and Tomatoes ($.35),2;”
Do you have control over how this string is built? If you do, you could
move the quantity to the front, and the "toppings" (I'm guessing) to the
end. That would leave the first 3 fields as fixed (assuming no commas
allowed), and the remaining comma delimited values as "toppings". Doing
that would make it much easier to code it.
Aside from that, this line seems to be the problem:
<MvASSING NAME = "l.tempextra" VALUE = "{miva_variable_value('g.extra' $
l.counter)}">
the "MvASSIGN" is spelled wrong in the code, and it's using 'g.extra'
which is never assigned.
should be:
<MvASSIGN NAME = "l.tempextra" VALUE = "{miva_variable_value('l.extra' $
l.counter)}">
--
Bill Guindon (aka aGorilla)