View Single Post
  #12 (permalink)  
Old 07-31-06, 04:43
chris.jurado chris.jurado is offline
Registered User
 
Join Date: Jul 2006
Posts: 10
Quote:
1 You are using acronyms which have meaning but you have a private definition (eg. FIFO)
That is not a private definition. It is understood in the realm of cost accounting. I was hoping for someone knowledgeable on Inventory costing. I've studied FIFO costing through multiple sources (books, internet). It is what I understand of it. And I may be mistaken in my understanding. I'm not all-knowing and perfect. So go ahead and correct me if I'm wrong. We are here to learn.

Quote:
2 You have already decided what is meaningless and meaningful (rather than completing the analysis before making that decision; rather than letting us make that decision). Therefore all the cards are nto on the table.
What "cards"? Why don't you tell me exactly what information I did not give necessary to solve the problem? You are being too general.

Quote:
You have not "explained the problem pretty well at all".
Each is entitled to his own opinion. And some people understand, some don't. If you can't understand, why don't read the problem very well and ask specific questions? If you really wanted to help, that is what you should have done. Like what Certus did.

Quote:
3 You do not appear to appreciate that db design, modelling, is the result of a process of normalising the data, INDEPENDENT of the processing [eg. programming] needs. You are focussed on your processing needs, which is understandable, since you have gone through many mods, etc., but it IS a limitation. Modelling will put cats and dogs in the correct tables, allow joins to animals, etc. I do not intend that as analogy, I intend it as a completely removed example.

If you want to explain the problem, give us your input forms and your output reports.
I am not here designing a whole application/system. It IS only a part of it (some procedures) that we are discussing. We need a design or pseudo-design that will make these procedures efficient and flexible.

1. Calculating next cost of sales for a stock transaction that deducts from inventory.
2. Adjustment/Cascading/Correction of cost of sales after editing/deleting stock transactions that deducts from inventory.

I already gave all necessary information (data, fields, sample transactions) for the problem. I cannot "lay all the cards". That is impractical. All that information will already make a book. I will only give the necessary. If you think some information is lacking, be specific. Tell me what.
Reply With Quote