Hi

>You may need UDFs here and there. But in this specific case, I think that it would be simpler to use variables and arrays which you accumulate while you evaluate the formulae (1) one line at a time, and perhaps do some replacements, in some cases, to make it more logical for the end-user. Note that an array element can be written as TotalLine(3) or TotalLine[3].

Okay.

>Ah, yes, the flexibility. That reminds me of a joke about confessions. (Note: The majority of South America's population is Catholic (Christian), and the Catholics have a custom of regularly confessing their sins to their priests.) One man confessed that he stole one half of a slaughtered pig from his neighbor. The priest had just installed a new computer system to help him in his work, tries to input the data, and then tells the man: "Go and steal the remainder of the pig; this machine doesn't accept decimals".

<g> But this is the truth, at time my applications are pretty inflexible and I end up with more work in the future than I would like.

>Anyway, you will have to think whether you want to use the same rounding rules throughout the system, or give the users the flexibility of adapting in individual cases.

I guess we can go for a global setting which applies by default, except overridden in the grid. This will help in other reports which seperate the invoice into items wise for reporting. So if a user selects rounding to 0 dec. when I split the invoice for reporting and calc. round(qty * rate, m.userround), as far as the grid calc is concerned I can have a field for round which is filled by default by the value set in m.userround and the user can override in the GridMaster table. What say.

>(1) I understand that the plural of "formula" is either "formulas" or "formulae". I prefer the second, although it is less common <g>.

I was worried formulas would be wrong, so I stuck to formula <g>