RStewart

Apologies if that has been discussed before: If you import a set of records with the 'update existing' option checked, and the imported set has to records with the same key field value, which one will take precedence? The latter one? Example: I am importing part number counts into the db. What if I have the same number twice in the set that is being imported (the first one being a value of 6 the second being a value of 9) Which will end up in the db?

Ok, I'm building a parts inventory file that has the ability to track multiple quotes form different vendors for each part. I would like to be able to show the price breaks for any given quote: (i.e if you buy qty 0-10 you get this price,10-20 gets this price, etc) Because these vendor quotes are already in a separate related file and given that only 500 out of 10000 records will use this feature, my feeling is that a third related file is a waste / unnecessary burden . I was thinking perhaps a repeating field for the each of the breaks. The question is , however, how do we extract the right price when the user is entering the part into a PO. I was thinking it might also simplify things if we designated one particular repetition as the default (which would be good since we have economic order qty defined as well). But even then I am not quite sure how to make the repetition show through....

So basically i should keep line items separate and then use scripts to post inventory debits/credits to a separate stock file? The one down side with adjustments, i have found, is that if you make an adjustment and then someone comes along and eventually corrects the cause of the initial variance, then you get a situation where you are over corrected (so to speak) I suppose there are work around for this (aside from requiring people to think about something while doing it ) Great idea about using a daily qty for the stock levels....Definitely going to explore that option further...Thanks

We are in the planning stages of a new live inventory system for my company... My question is two fold: When dealing with "line items" that will effect inventory levels, is it a good idea to have the line items share a common file? (so that purchase orders and sales orders both store line item data in the same file) Or is better to use separate line item files? Second question: Does anyone have a pointers (or links) to some ideas on how to handle year end inventory/stock counts? The inventory levels need to be reset to the qtys that were counted at year end; but, we still need to refer back to the previous year's data. I would like to avoid cloning the file set and starting fresh. The first time through i used a transaction number to calculate if a given transaction should be included when tallying inventory (example:For each transaction "IF CutoffNumber < TransactionNo then StockQty=Qty else StockQty=0) This of course became quite a burdensome overhead on the system to calculate after 70K line item records had been added. I was thinking about just using a field to flag records and then perform changes via scripting (since it would only be done once a year anyway) I am curious, however, to see if anyone has a different approach on this issue or even some recommendations on archiving practices or methods. Thanks in advance for your efforts.