Sage 100

Got a call from a customer that uses DSD's Sales Order Shipping Integration - they updated their UPS WorldShip software to the new version 20, 2017 level this morning and now the Key Import doesn't come up and gives error if you click on it from the keyed import drop down. The ""ImportMAS"" mapping cannot be brought up to edit either. My guess is that it's something in the UPS update that is stopping the keyed import. Just wanted to put this out there to see if anyone else has run into this and to let people know who have end-users using this. Remind them to not update software with an integration to Sage 100 without running it by their Sage consultants. Now their failure to plan has become my emergency!

first, the customer needs to understand that the keyed import has nothing to do with Sage or Shipping Integration. Shipping Integration only comes into play AFTER the shipment is completed. I would recommend that you check the ODBC settings first to make sure that they are working to reach Sage database. That is usually the cause of the Keyed Import not working.

Cooper, thanks for the feedback, I will check the ODBC, odd thing is, was working fine yesterday, this morning not working, only variable changed, is UPS Worldship software updated to new level.

What about the user logged into windows? Is that different? Sometimes the ODBC is setup as a USER DSN and not a SYSTEM DSN and a different user may not have the right ODBC set up

Cooper, you are a genius! that was it! Shipping station user swore nothing else had changed. Thanks!

Glad to help

The users are usually *clueless* as to whether something has changed or not.

Or they think something changed when it didn't change at all :)