Sighhh....
Because it's how every single stock control program in the world does it.
And I don't want it to change the price, just the cost. What I do need to know is what the real total value of my stock is at any moment, not what its notional value would have been 9 months ago when I set the file up. That's of no value to me whatsoever. And the pimply faced youth can make a lot of other mistakes besides this one - how come you're not bothered about that?
Anyone who you have laying any kind of finger on the system where sensitive data is concerned - and just receiving stock would fall into that category -
should be a trusted employee - not some oik you've just dragged in off the streets. Firms do have them you know. They work in places like accounts. Employers also often train them too, to do things properly strangely enough. You have to do that when you expand beyond just being a one man band and doing every ruddy thing yourself.
But never mind. It just means that DHPOS will always only really cater for the single owner Mom and Pop store who just want to bang out nice looking receipts and wouldn't know what stock control was if it came up and bit em on the backside. And so long as you're happy Dale banging out monster features like ticket sales, that only one person in the world apparently wanted, that's OK
PS - the amount of code needed would not be great. And to satisfy reluctant revisionists like yourself, Dale, you could even add a switch in POSConfg so you could decide whether to update stock cost or not on receiving stock. But everyone would leave it in 'Yes' anyway.
