>Damn it, the first thing I have to do is look up some of the technical terms (bookkeeping, taxes, etc.), which I may, or may not, have heard in Spanish...
<g> I am sorry to have overloaded the message.
>>In it I will have a column for Line #, AcctID, Percentage, Amount (if a % is specified I will have to fill in Amount, else the user presses enter and fills in the Amount, they will be one or the other), ...
>
>IIRC, what I did in a similar situation is to put both a percentage and an amount. If the user left the percentage zero, an absolute amount could be used. If the user specified a percentage # 0, any amount would be overwritten.
Agreed
>I am a little confused, with the details.
I am sorry to have confused the matter, but it just struck me and I was demolished that all the ideas would be coming to nil as the excise had to be calculated on a line item basis and not on it's total
>But if you need to apply certain formulae to all line items, one by one, that should be possible, too.
Can you provide and eg. in this grid concept, ie. what kind of text to store in the Grid.Formula field that could be eval()
>It seems you will have to apply rounding functions, either automatically for all your calculations, or by giving the user the possibility of applying round() or a UDF.
Maybe another grid.field let's say Grid.Round which can have 0, 1, 2, or whatever the user wants and we can wrap the eval() with as such ROUND(EVAL(Grid.Formula))?
>BTW, for applying formulae which will be evaluated with eval(), it seems convenient to give the user a guide of common VFP expressions, which might include:
>
>
Use an asterisk for multiplication.
>round()
>Priority of operators, for example, 1 + 2 * 3 = 7 (not 9). Use of parentheses.
>Some common VFP functions.
>Any UDF you find convenient to include.
Yes, thanks.
