RE: OCBC performance with UPS Worldship

Dave,

We had a similar problem with Worldship in our shop. Even though we had one
file to export addresses and one file to receive shipment details,
performance was horrible (one transaction took minutes). We tried the other
suggestions I've seen and nothing helped.

Then I noticed that while editing the Import and Export maps, every field in
every file in the library specified in the Client Access ODBC data source
was available. We moved the files to their own library, and performance is
now acceptable. Apparently every time Worldship made a connection, it was
scanning every field in every file in the library to find the ones it
needed.

So if you are trying to go directly from/to your live files, I suggest you
use an export file and an import file and put them in a separate library.
Then specify only that library on the OCBC data source on the Worldship box.

HTH,
Roger Mackie
--------------------------------

>I am working on connecting a PC with UPS Worldship software via ODBC to the
>AS/400 for a client.<snip> From the time the "Process Shipment" button is
clicked, >it takes 30+ seconds to complete a single shipping transaction.
If I edit an
>existing transaction, the entire process can take 45 seconds after the
>"Process Shipment" button is pressed.  I am not too excited about this type
>of response.
<snip>
>I will be trying a "live" test on Monday and would like to have some
>possible solutions in hand.

>Thanks

>Dave Murvin
>DRM Enterprises, Inc.
>davem@drme.com