Here is the how to for MOM 6.0
This will take care of a one time import. If you are working with a single supplier than it would be easy enough to wipe out the purchase table and import the new purchase information each time.
I agree that Dydacomp should have packed this feature or an add on solution into V6.
AIM will not import this purchasing level information. You can update the BUYPRICE.DBF information directly using DBUWIN if you follow some specific steps.
- Have everyone out of M.O.M.
- ***MAKE A FULL BACKUP OF THE ENTIRE MOMWIN FOLDER**
- Run DBCMANAGER.EXE out of the MOMWIN folder
- Detach BUYPRICE.DBF from the database container
- Close DBCMANAGER
- Run DBUWIN.EXE out of the MOMWIN folder
- Open BUYPRICE.DBF and add your records (please let us know if there are questions, you don�t want to do this wrong)
- Close DBUWIN when done
- Run DBCMANAGER.EXE
- Attach BUYPRICE.DBF back to the database container
- Open M.O.M.
- File -> Reindex System Files
David,
thanks for the info! I am 2 years late seeing your response :0 I see that I have made a couple of mistakes for a long time (1) been running dbcmanager in MOMWIN, (2) been running DBUWIN in MOMWIN, (3) have not been detaching buyprice before apending to it.
We always import one vendor at a time as they get updated at different times of the year. If we wanted to effectively reimport the "current product file" each time, what would you recommend? Do we have to remove any open (BO status) products for this vendor from any orders or would it be ok to leave them? What steps would I need to take to use DBUWIN to filter and delete all the products for that vendor from the STOCK, BUYPRICE, and BIN files and then reimport them (using stock import utility for the STOCK.dbf and dbuwin to append the BUYPRICE and BIN.
The bottom line question is what do I need to do to WIPE OUT the existing product information and then reimport the "new" products for a specific vendor. I can simply run the import and then MOM will tell me how many were imported, how many were duplicates, etc. The problem with this is that it leaves the old product in the DB cluttering it up, it also does NOT update the pricing on existing products so I have to use dbuwin to manually update the prices by setting up a relation, I have to append to the BUYPRICE but before doing that I have to delete the records that already exist so they are not duplicated, etc, etc. A REAL PAIN!!!
thanks for any help you can provide.
Tim Durham
A2Z Uniforms, Inc.