Well obviously a script, but I suspect you already know that. Possibly use a user-defined table to store the results which gets to be a rather "fun" project.

Might I ask what you will be doing with that information that you have captured?

I thought about a UDT, but that's going to be messy, I think. I'm hoping there's a way to store something in "memory." I'd like these running totals to be accessible for use in other scripts that will be executing at various trigger points during SO Entry.

I remember that there is a way to share variables like that, but would you think I could find the info?

I thought I read something like that. Maybe someone will post it. Thanks!

You didn't answer as to what you would be doing with that info gathered.

I ask because their are features built into the program to do things like quantity discounts based on product lines quantities or total quantities on an invoice (which is the primary reason I would think of doing this). Sales Order Options | Tab 3

If you want summaries by product line on the actual invoice, it might be easier to do that in the crystal forms.

In any event, what you want to do with the info might suggest other possibilities.

I actually need discounts by total skids/pallets per product line. So I'm not actually using the quantity ordered, but a UDF that has the total number of skids. (That conversion varies by item number and another script is used for that.) So the product line pricing discounts won't work in this case.

Yea Kevin!

With that found, it brings up a different question in my mind. Does the providex scripting allow for array variables?

I would imagine it can, I've just never needed to do it. n0tgunshy1's project would seem to require it.

Normal BOI scripts are .vbs, not providex.

So if I am writing a script using oBusObj and Oscript, etc. are arrayed variables available?