Updating stock in Access Table

Galaxiom.

I meant to ask how the rain was affecting you.

Hope it doesn't destory any important crops. :D ;)
 
Sorry boss we are missing a $100,000 Merceds. But the program balances because I made an adjustment.

While the Serial Numbered items like a Merc are unlikely to need adjustment, the concept of a stock adjustment transaction is absolutely essential to typical systems.

Units may be damaged, lost or stolen. Unless a transaction is entered to adjust the stock then there will be no possibility of reconciling the stock on hand with the sales and purchasing transactions.

I have never seen a system where a stocktake count is applied by simply adjusting a stock on hand figure in the inventory file without recording some kind of transaction. Such a notion would be ludicrous.

Indeed it is the continued adjustment of the stock on hand figure and the possibility of errors that makes experienced developers eschew keeping a figure in the inventory file.

Where it is impractical to calculate a stock figure from day one of the system I suggest the stock on hand figure is updated periodically and the current figure calculated from the last update and transactions from that date forward.

This avoids any problems with multiple users trying to update the stock level at every transaction and the possibility of failure.
 
Galaxiom

I am not sure if you are agreeing with me or not.

Please clarify.
 
Last edited:
When it comes to storing calculated values I half agree.

Storing calculated values should be generally avoided but sometimes they can be justified. However I feel many developers too easily justify it.
 
Storing calculated values should be generally avoided but sometimes they can be justified.

Galaxiom,

I am in some ways agreeing with you but I would like to explore the issue further.

I am challenging those who simply say that you never store.

If you have the time could you please cite a couple of examples of where you would say it is correct to store and where would you say it is incorrect.
 

Users who are viewing this thread

Back
Top Bottom