Re: Fed Ex Rate Charts
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 48629
interpreted = N
texte = On 3/12/03 10:26 AM, Jesse Williams-Proudman
wrote:> On 3/12/03 4:58 AM, Gary Krockover wrote:> >> Should you be using:>> http://fedex.com/us/rates/downloads/pdf/all_zones.pdf?link=4 is the link for>> rates by zone. (or in ASCII format:>> http://fedex.com/us/rates/downloads/ascii/2003_FedEx_US-Express_RatesByZone.>> zip?link=4)> > Yes, I got that part. So I know what zone my client is in, and I can figure> out what zone the ship to customer is in, so then how do I calculate the> rate between the two based off that table because it never asks you to> specify an origin zone, just the final zone...> There may be a misunderstanding here. FedEx generates a Zone chart based onYOUR location (the origin), thus, when you plug in the destination zip codeyou get the shipping zone based on shipping from YOUR location to thedestination. Once you have the zone you use that on the rate chart as one ofthe inputs (the other is weight). Thus it is a two step process: 1) getzone, and 2) get rate.Does this answer your question, or have I gotten your question wrong?Cheers,LurchWebmaster and Virtual Barkeep Emeritus......Lover of fine whisky, fast women, and faster airplanes......not necessarily in that order :P-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
On 3/12/03 10:26 AM, Jesse Williams-Proudman wrote:> On 3/12/03 4:58 AM, Gary Krockover wrote:> >> Should you be using:>> http://fedex.com/us/rates/downloads/pdf/all_zones.pdf?link=4 is the link for>> rates by zone. (or in ASCII format:>> http://fedex.com/us/rates/downloads/ascii/2003_FedEx_US-Express_RatesByZone.>> zip?link=4)> > Yes, I got that part. So I know what zone my client is in, and I can figure> out what zone the ship to customer is in, so then how do I calculate the> rate between the two based off that table because it never asks you to> specify an origin zone, just the final zone...> There may be a misunderstanding here. FedEx generates a Zone chart based onYOUR location (the origin), thus, when you plug in the destination zip codeyou get the shipping zone based on shipping from YOUR location to thedestination. Once you have the zone you use that on the rate chart as one ofthe inputs (the other is weight). Thus it is a two step process: 1) getzone, and 2) get rate.Does this answer your question, or have I gotten your question wrong?Cheers,LurchWebmaster and Virtual Barkeep Emeritus......Lover of fine whisky, fast women, and faster airplanes......not necessarily in that order :P-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Joe R. Richardson
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Need some Java Script Code (2003)
setting line item numbers (1998)
Limitations on fields? Server is crashing (1997)
[WebDNA] What is faster ? (2013)
Bug Report, maybe (1997)
Forms Search Questions (1997)
tab as word delimiter (2000)
Nested tags count question (1997)
redirect from the errorsMessages.db entry (1997)
Quickie question on the email templates (1997)
Getting Averages for online form. (1999)
A question on sub-categories (1997)
[WebDNA] v7 help (2012)
Moment of Thanks (1997)
Client-side Image Maps and WebCat? (1998)
Date search - yes or no (1997)
Security - 2 (1999)
Practice runs ? (1997)
RE: CloseDatabase (1997)
Max Record length restated as maybe bug (1997)