6 replies to this topic

[A2Z Uniforms]

Greetings other MOM users,
We have been with MOM since version 4. We currently use MOM 6.0 and the main reason we upgraded from 5.4 was for the Stock Import module. We found out that the Import Module does not write any data to the BuyPrice.dbf file rendering all of the imported stock useless because you have to manually enter all the buyprice data thru the Maintain Stock function.

Dydacomp has fixed many of the flaws in MOM 6.0 and this is the last of the major issues. How many of you out there would import stock if the Stock Import Module was designed correctly and 100% functional?

I am pushing for Dydacomp to fix this issue becasue it will be an invaluable tool for companies who have 100's and 1000's of products to import. It just needs to function properly.

I look forward to hearing back from other users.

Tim Durham
A2Z Uniforms, Inc.
Southaven, MS

www.a2zuniforms.com

[Wes Faul]

Tim,
It would definitely be handy to have this import. Every year we have to try to hack through adding records into Stock.dbf, Buyprice.dbf and Price.dbf. When we come out with a new catalog, I have spreadsheets of the items, costs, retail prices and our wholesale price. For this year, I'm using an asp.net script that connects to MOM, updates prices, buyprice info and price info (wholesale prices) as well as imports new products. My master spreadsheet is over 22000 lines long (over 22000 items...). Obviously, updating these by hand would be impossible.
I'm still in the process of testing my import to make sure that no problems arise.
It would definitely save me many hours if Dydacomp provided a way to import this.
Wes

Greetings other MOM users,
We have been with MOM since version 4. We currently use MOM 6.0 and the main reason we upgraded from 5.4 was for the Stock Import module. We found out that the Import Module does not write any data to the BuyPrice.dbf file rendering all of the imported stock useless because you have to manually enter all the buyprice data thru the Maintain Stock function.

Dydacomp has fixed many of the flaws in MOM 6.0 and this is the last of the major issues. How many of you out there would import stock if the Stock Import Module was designed correctly and 100% functional?

I am pushing for Dydacomp to fix this issue becasue it will be an invaluable tool for companies who have 100's and 1000's of products to import. It just needs to function properly.

I look forward to hearing back from other users.

Tim Durham
A2Z Uniforms, Inc.
Southaven, MS

www.a2zuniforms.com

[cataloger]

Dydacomp has fixed many of the flaws in MOM 6.0 and this is the last of the major issues. How many of you out there would import stock if the Stock Import Module was designed correctly and 100% functional?

I agree completely with you. I find it unbelievable that MOM does not supply a function to import selling prices and purchasing costs via the import tool. The lack of this 1 feature alone is making me consider switching to another software platform. I waste a lot of time updated vendor pricing.

[Videoflicks2004]

Hey,

I just purchased MOM 6 for a client and my tests on the database indicate that importing BUYPRICE via dbuwin is a piece of cake.

The table has only a handful of fields. It would be ideal to do it in the stock import but it is still 10000000 x better than mom 4.3 which had NO stock import at all.

I'll test this out further.

Dave

[planetdj]

I agree completely with you. I find it unbelievable that MOM does not supply a function to import selling prices and purchasing costs via the import tool. The lack of this 1 feature alone is making me consider switching to another software platform. I waste a lot of time updated vendor pricing.

With all of the wonderful features in MOM, we too believe that having a reliable, accurate way of mapping and importing a supplier's price sheet, complete with sku, description, cost, sale price, etc., is the #1 most important tool we are looking for. I spend WAY too much time and money paying data entry people to do it all by hand, only to find that they messed something up anyways! And some of our suppliers come out with a new price list more than 6 times per year!!

[Videoflicks2004]

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

[A2Z Uniforms]

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.