UPS Worldship with 3.6

avf

We have used UPS Worldship in earlier version of Navision with no problem. With 3.6, the initial ODBC connection to Navision takes hours. UPS has been no help. It seems that the software does some evaluation of the database during the boot up phase. Has anyone experienced this issue or similar issue with the 3.6 ODBC driver? Thanks.

bruno77

Yes, I have experienced the same problem. I solved it by going through a linked table and query in a Access database. UPS tech support told me that it was slow because the values are converted from Access format however when going trough Access to a Navision database it was not slow at all, so I'm not sure where the real problem resides.

Regards,

Bruno

jwilder101

Bruno,

I know that Worldship cannot link to a linked table in Access (please tell me if you know how to do this). Do you link Worldship to an Update table query in Access? Please tell me exactly how to do this.

Jason

Savatage

jwilder101 wrote:

Bruno,

I know that Worldship cannot link to a linked table in Access (please tell me if you know how to do this). Jason

This article discusses information about the use of 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.

MORE INFORMATION

This is because the ODBC drivers do not support parameter fields, which Access uses when external tables are linked.

Consider the following SQL statement that retrieves all records in all columns from the Customer table:
SELECT * FROM Customer

When you link a table in Access, the program creates an SQL statement that looks similar to this:

SELECT * FROM Customer WHERE Field1 = ? OR Field1 =? OR Field1=?

Access always retrieves ten records at a time. Therefore, the above statement will contain ten question marks. The question marks points to memory addresses that are updated each time you request a new page of data in Access. The values in the memory addresses for the first statement will be 1,2,3,4,5,6,7,8,9,10 if the first ten customers are numbered sequentially from one and upward. In this manner, the SQL statement becomes dynamic in the sense that Access only has to update the memory addresses with the values for the next ten records and call the SQL statement again to retrieve the next ten records.

However, dynamic fields (parameter fields) are not supported by Navision ODBC drivers.
There is a workaround that involves changing an entry in the registry database in Windows.

1. Find the following key in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Access\7.0\Jet\3.0\Engines

2. Create a new key named ODBC(if the ID does not already exist).

3. Create a new DWORD named SnapshotOnly with value = 1 in the ODBC key.

4. Now linked tables can be used in Access.