Sage 100

Have a client on Sage 100 Adv 2016 (newly upgraded). They have an office in another state (from the Sage server via WAN) using the UPS Worldship keyed login feature to fetch sales order info from Sage into Worldship. This no longer works consistently (most of the time it times out after taking a really long time to connect after providing Sage credentials) Is this something the Client Server ODBC can fix? Anyone have any other suggestions? TIA

Are you using an Access intermediary between Worldship and Sage 100? The CS ODBC may help, but sometimes Access linked via ODBC can get the Providex ODBC to behave better...

Yes CS ODBC should help. I've done that for the Worldship silent connect ODBC System DSN before for 2 shipping PCs that were part of the same LAN actually but tremendously slow (just fill out the Server tab after you get CS ODBC configured working from elsewhere then click Test Connection to make sure it works) . I considered the Access intermediate soln first for them but no Office on those machines and I wanted to get the hell out of that whse as fast as I could.

We had similar issue. We used VI to dump SO_Header table to an access DB and then pointed the Worldship to pull from access instead of live MAS. We exported every 30 minutes so that we got relatively fresh data.

After burning tons of time years ago trying to get the sotamas driver to work with UPS, my go to connection is always the access PTQ on the server (safer location). Not sure which location would be faster in your case though. @CooperBlack if you link using a PTQ, no refreshing is required. Information is real time.

Third vote for using Access DB and if you have a good UPS tech, they'll write a file output for you, csv, that you can use to import the UPS tracking numbers to the invoice data entry before update.

DUH - they have SQL Mirror. Thank you all for helping think outside the box.

@MyronStevenson wrote an Access script for me that puts everything into Sage just by click a button. No importing necessary.