Re: Price Not Appearing

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 28443
interpreted = N
texte = on 03/02/00 9:02 AM, jpeacock@univpress.com at jpeacock@univpress.com wrote:> Do you have a field called price in your database? If you do, change it to > my_price (or anything else). When you are inside an orderfile context (either > implied or explicit), the field [price] from the orderfile will override any > field of the same name in the database. The best methodology to follow is to > assign the appropriate price at the point a line is added to the shoppingcart > (usually through the use of formulas.db).Thanks. I tried changing the name of the price field to myprice. It worked on some pages, but not on others (as did just using price), so I revised the database to have a field for price and another for myprice. This sorta worked, but it just doesn't seem right to have to work around a problem this way. Assigning a field value through a formulas.db seems just as left-handed, especially when the data is already entered in the database.I'm going to start over from scratch....dammit.Thanks for all the help, guys. I really do appreciate it.Glenn ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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 Associated Messages, from the most recent to the oldest:

    
  1. Re: Price Not Appearing SOLUTION (Glenn Busbin 2000)
  2. Re[2]: Price Not Appearing [LONG] (jpeacock@univpress.com 2000)
  3. Re: Price Not Appearing (Glenn Busbin 2000)
  4. Re[2]: Price Not Appearing (jpeacock@univpress.com 2000)
on 03/02/00 9:02 AM, jpeacock@univpress.com at jpeacock@univpress.com wrote:> Do you have a field called price in your database? If you do, change it to > my_price (or anything else). When you are inside an orderfile context (either > implied or explicit), the field [price] from the orderfile will override any > field of the same name in the database. The best methodology to follow is to > assign the appropriate price at the point a line is added to the shoppingcart > (usually through the use of formulas.db).Thanks. I tried changing the name of the price field to myprice. It worked on some pages, but not on others (as did just using price), so I revised the database to have a field for price and another for myprice. This sorta worked, but it just doesn't seem right to have to work around a problem this way. Assigning a field value through a formulas.db seems just as left-handed, especially when the data is already entered in the database.I'm going to start over from scratch....dammit.Thanks for all the help, guys. I really do appreciate it.Glenn ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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 Glenn Busbin

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:

authnet good news (2003) 2.0 Info (1997) New Guestbook Source (1997) WebCat2 as a chat server? (1997) international time (1997) In Digest Dijon (2000) Formatting (2000) Calculating multiple shipping... (1997) Emailer (1997) Running 2 two WebCatalog.acgi's (1996) Looking for a Manual (1997) Limiting user access to .tmpl files (1997) Why are some admin pages not encrypted? (2000) WebCat2b13MacPlugIn - [shownext method=post] ??? (1997) Progress !! WAS: Trouble with formula.db (1997) Database Upload (2000) Code ideas req: Matrix of users and options [code] (2003) FYI: virus alert (1996) Roundup function? (1997) Bug Report, maybe (1997)