Sage 100

Has anyone done a Sage 100 2013 to Worldship connection? The client currently has a working v 4.3 to Worldship. I changed the ODBC path, it tests fine and connects according to Windows. Since it was setup on 4.3, the file names should be the same, but it won't connect to 2013. Anybody run into this before? Do you have to complete rebuild the Worldship connector in Worldship?

I've done a few upgrades and not had to rebuild the connector in WorldShip. what error are you getting. are you just connecting via ODBC to the Sage Database, or using CrossWare or ShipGear? .

Same here. I have it running in 2013 at one site, but we didn't have to do anything to the Worldship connection.

Is 2013 active on workstation when accessing WS?

It's been some time since I've messed with one, but this one is configured a bit differently. Worldship is accessing a mirror table in Access to pull the data. There is a MAS ODBC connector that populates the table in Access. It appears this is where the issue lies. I'll have to dig into Access and see what's happening. I changed the DSN and then Access will kick out an error, even though ODBC test's fine in Windows. I usually just create a new DSN and have Worldship run through that, but it didn't like that either.

@JeffSchwenk - yes 2013 is active when WS is pulling data.

Fixed... changed the ODBC connector that the linked table was using and corrected the problem.