I am in the process of trying to integrate UPS Worldship with Navision 3.7. I am using Access 2003 as an intemediary and have all my mappings done. When I try to import shipment information into UPS Worldship using the Keyed Import tool, I get the following error: ODBC ERROR: State = S1000 Error = [Microsoft][ODBC Microsoft Access Driver] ODBC – Call failed. When I select OK to clear the message this comes up: “No data found for the given key value.” I can not figure out where the connection is failing. I have checked and rechecked my mappings and tables and do not see a problem. Does any one out there have any ideas what is causing this. Any information would be greatly appreciated. Thank you.
here’s a similar post. Maybe you can email some of the people who have it working sucessfully. http://www.mbsonline.org/forum/topic.asp?TOPIC_ID=11007&SearchTerms=worldship ??Are you using linked access tables or a single table.?? I believe there was an old issue about Microsoft Access together with ODBC in Navision. It is related to the fact that problems may occur when using the tables in Navision as linked tables in Microsoft Access. This can give strange results after the table is successfully linked, but when you try to go to the next page of records, the data becomes corrupted. I don’t know if it’s been fixed in the newer versions.
I just did it yesterday. Here are the steps. 1)Create a Navision ODBC connection 2)Create linked table in Access 3)create a query if you want to filter out some data 4)create ODBC connection for access database 5)create mapping
Although you will resolve this ODBC issue, World ship is quite a complex little beast. In the long run you will be better off if you use a C/FRONT interface. It will look like a lot more initital investment, but will pay dividends down the road.
Lanham (www.lanhamassoc.com) has an add-on called “E-Ship” which has UPS integration that works fine in US. /Karl
Yes eShip is a great package, and offers a lot. At the least do a comparison between eShip and continuing with World Ship. Though you may have business reasons that will force you to stay with World Ship.
David, I am in the middle of a similar project. One shipping station up and another to go in a different department. The key to success with Worldship appears to be making sure that the Access intermediary database has linked tables to Navision and then Queries defined that mirror those table definitions. Unless I reference the query with the mapping it takes FOREVER because Worldship wants to cache the definition of every table in Navision before it starts talking to you. Always map to the Access Query, not a linked table. Good Luck, Mark Tyler