ufsimatt

Although I do not know of an easy systematic way of getting MOM to include the rural surcharge for FedEx, or any other of the charges that can filter in for a package through FedEx, on your invoice, perhaps you should consider moving to a single flat shipping charge. If you analyzed your shipping destinations and packages factoring in the weight of your average package and the cost to ship that package to the furthest shipping zone from you, you can begin to get an idea of the most a package could cost you. From there you could see where most of your packages fall zone-wise and determine a flat rate that over all packages would cover your costs for a particular service, say FedEx Ground and/or Home Delivery. If you are shipping a large number of packages to areas that are consistently charged the rural charges, then I would definitely suggest moving to a flat shipping rate or looking at offering a different service, say USPS with delivery confirmation, as an alternative to help you with your costs. I am a partner in a fulfillment company and many of our clients go to some form of a flat shipping rate to counter these very same things that you are mention. Best of luck!

ufsimatt

The .cdx files are the index files for the database table (.dbf) files. If you choose to use the Reindex portion of MOM, then what you are doing is recreating these .cdx files. If you have ever called Dydacomp for support(and survived the lengthy wait on the phone) you very well could have been told to go delete one of the .cdx files as part of the solution. All databases FoxPro or otherwise, have indexes on the tables; how they store them and whether they are expressed as literal files like FoxPro, is a different story.
Ultimately, the .cdx files are very important without them MOM won't run, by the same token, if they become corrputed or you delete one, MOM will recreate the .cdx file when you launch MOM again. I hope this answers your question.

Best,

Ufsimatt

If by RR you are referring to Report Writer, then you should easily be able to do it with that program, by selecting the CUST.dbf and then putting the fields you want on the report. Then do a file export to a worksheet format or some other format and you should be good to go. Alternatively you could accomplish the same thing using MS Access. If you have any other questions or would like some help feel free to email me, [email protected].

Although I do not know why MOM only exports 16,000 rows instead of everything you have, it doens't particularily suprise me. If you have report writer, I would suggest recreating your report in there; I have had a good deal of success with report writer and find it way better then the standard reports from MOM.
If you have Access you can always link the MOM tables that you need and run queries to find the information you want and handle the data anyway you want at that point.
As to your desire to have the DESC and DESC2 fields be longer then 30 characters, you are out of luck as far as I know. For whatever reason, the MOM tables and program were written with this limitation and unless Dydacomp changes their table designs for future versions, I don't believe there is anyway around those issues.
If you would like some more help concerning your report/export problem, feel free to send me an email or message through this board and I will be happy to talk to you about it some more.

I've had orders in the past that seem to get caught at this point as well. I seem to recall that resetting the order status and run order processing just for this order has worked before. If that doesn't work, you can try resetting the order, delete the item, reenter the item, save the order and try processing the order by iteself again. Good Luck!