Microsoft KB Archive/217753

= DOC: TableShippingADO Should Not Follow the DefaultShipping Component =

Article ID: 217753

Article Last Modified on 7/14/2004

-

APPLIES TO


 * Microsoft Site Server 3.0 Commerce Edition

-



This article was previously published under Q217753



SUMMARY
In the Site Server 3.0 documentation under the topic, "How to use TableShipping," it states:

The TableShippingADO component should always be inserted after the DefaultShipping component in the Pipeline Editor. The DefaultShipping component ensures the integrity of the OrderForm's _shipping_cost name/value pair by setting it to an initial value of zero (0). If you insert the TableShippingADO component, or any other shipping component, before the DefaultShipping component, the _shipping_cost name/value pair will be overwritten.

In fact, if the DefaultShipping component precedes the TableShippingADO component, the TableShipping component will not be executed. In order for the TableShippingADO to work, the DefaultShipping component must be removed from the pipeline.



MORE INFORMATION
The "Component Coordination" topic for "Pipeline Components" notes:

By convention, components cooperate and do not overwrite a previous component's results, unless the overwriting component is specifically designed for that purpose.

Other references in this help topic suggest that the shipping components are an exception to this rule.

Keywords: kbdocfix KB217753

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.