IT SOLUTIONS
Your full service technology partner! 
-Collapse +Expand
Delphi
Search Delphi Group:

Advanced
-Collapse +Expand Delphi To/From
To/FromCODEGuides
-Collapse +Expand Delphi Store
PRESTWOODSTORE

Prestwood eMagazine

April Edition
Subscribe now! It's Free!
Enter your email:

   ► KBProgrammingDelphi for W...Using Data   Print This     
  From the December 2008 Issue of Prestwood eMag
 
Delphi Using Data:
UPS Shipping API 120971 Warning problem
 
Posted 13 years ago on 1/10/2007 and updated 12/2/2008
Take Away: On January 1, 2007, merchants using the UPS shipping API began experiencing a serious problem. Prestwood has found the solution.

KB100437

On January 1, 2007, merchants using the UPS shipping API began experiencing a serious problem. One of those merchants happened to be one of our clients.

The problem manifests itself as a new "warning" message being returned as a result of the Ship Accept API call. 

While this is only a warning, if existing code isn't prepared for it, it will most likely be treated as an error.  In the case of a web check-out page, the end user may see a message that says

"Your invoice may vary from the displayed reference rates."  

Worse, the code behind the check-out page probably doesn't know what to do next. As you can imagine, that can't be good for business!

In the case of our client, no web display was involved.  Instead, we wrote a  DLL that allows his custom business software to utilize the UPS on-line shipping services.  The error manifested itself as an error dialog, and the rest of his shipment processing was halted.

At the time we created that DLL, we had no way to anticipate that UPS might alter their API such that, in the future, warnings would be returned via the specified error mechanism.

It took us several hours of research to get our "heads around the problem," less time to make the actual fix in our DLL.

The good news is that we now understand the problem, and know what to do about it.

Unfortunately, there are two problems with including example code here:

  1. The design and implementation of our DLL is likely to be quite different than other, existing solutions, so our code would lack context.
  2. Our custom DLL is the intellectual property of our client, and we're constrained to treat his code as containing "trade secrets."

That said, if you're wrestling with this particular problem, Prestwood can help. To get started, refer to the bottom of this page.


Comments

0 Comments.
Share a thought or comment...
 
Write a Comment...
...
Sign in...

If you are a member, Sign In. Or, you can Create a Free account now.


Anonymous Post (text-only, no HTML):

Enter your name and security key.

Your Name:
Security key = P136A1
Enter key:
KB Post Contributed By Wes Peterson:

Wes Peterson is a Senior Programmer Analyst with Prestwood IT Solutions where he develops custom Windows software and custom websites using .Net and Delphi. When Wes is not coding for clients, he participates in this online community. Prior to his 10-year love-affair with Delphi, he worked with several other tools and databases. Currently he specializes in VS.Net using C# and VB.Net. To Wes, the .NET revolution is as exciting as the birth of Delphi.

Visit Profile

 KB Article #100437 Counter
5930
Since 4/2/2008
Go ahead!   Use Us! Call: 916-726-5675  Or visit our new sales site: 
www.prestwood.com


©1995-2020 Prestwood IT Solutions.   [Security & Privacy]