I have a Point of Sale system that I made. I have a quantity field for the inventory items. It is a calulation of QTYsold and ShelfCount.

QtySold is a summary field of all the times that item sold and count is an editable field that is the count of shelf items. It continues to get added to the more we sell an item.

Example: We have 9 pcs in stock, and sell them all. Count is at 9, QTY sold is at -9, QTY on hand field now shows 0.

We get in 5 pcs count is now 14, QTY SOld is at -9, QTY on hand field now shows 5.

Any better ideas? This one seems crappy.

Edited March 21, 200718 yr by Guest

My feeble brain would probably handle it in a similar way, so I don't know why you think it's crappy...?

About the only thing I'd handle differently is that I'd want the QTYSold number to be positive so that I could easily see how much business I'm doing.

A fuller description of your structure would allow others to offer other suggestions, though.

David

count is an editable field that is the count of shelf items

How can it be in a summary report? You can't really use summaries in browsemode, except in the header or footer area, next issue is that they require a sortorder even if GetSummary( is involved, which is a little bothersome of the transactions comes in arbitrarily.

Strictly speaking should it neither rely on summaries nor on aggregate functions, but instead looking up the previous records transaction sum of the same itemtype, which is much more conveniently done with fm8.5's list function ...than with previous versions, where clever Ugo'ish relations takes care of getting the right data ushered in.

But you could do something else:

http://www.kevinfrank.com/download/kf-fast-summary.zip

Only thing is that the script needs to get trigged....

--sd