Re: ODBC performance with UPS Worldship

[Douglas Handy <dhandy1@xxxxxxxxxxxxx>]

Dave,

>At the present time, they do a batch import for the addresses once per day.

What is the rationale for doing this instead of just setting up an import map
and retrieving it dynamically when it hits the scale?

>The UPS machine just writes the shipment information to an AS/400 physical file

Without a trigger attached, then the delay would seem to be happening in the
ODBC insert/update side.  Does the physical file have a key?  Any logicals with
unique access paths?

>The client wants to use the
>immediate UPS shipping updates because they run billing periodically
>throughout the day.

In my case, the shipping must be processed immediately by the 400.  The customer
can opt to have the invoice sent attached to the package rather than mailed, and
the majority do it that way.  So as soon as they process a shipment, the 400
must update the order shipping charges etc then when applicable, assign an
invoice number and immediately print an invoice at the scale.  Customers who
prefer to have them mailed get theirs printed in a batch run later.

>I believe I have solved the mapping problems by exporting the UPS "numeric"
>type fields into their default size alpha fields on the AS/400,

I had tried alpha fields (parsing the value is no problem), but couldn't get
that to pass data reliably either. :(

>If I can't solve the problem with blocking adjustments, I will probably try
>the 3rd party ODBC driver mentioned in another response.

The third party drive I used was the same one (HiT Software), and it worked from
the very first attempt with no changes.

Doug