numero = 46470
interpreted = N
texte = This can be easily resolved by putting the expiration months/years into pulldown menus. It has been my experience that visitors/customers will enter all types of crazy things into text fields. So, I try to use radio buttons, checkboxes, and pulldown menus as much as possible in my forms as well as using javascript validation on the text fields.I've always said: If you give a web user the ability to screw up form field, THEY WILL! On 12/20/02 5:20 PM, Gary Krockover wrote:> Folks, > > The following is a copy of an email that I sent to Terry Wilson, who's a > list member that has provided much help on the A/N issue(s). I found that a > client of mine was receiving about 30% failure rate on orders, all with the > error of Expiration date invalid. The other 70% of the orders were > passing fine. This is using A/N and the ADC Relay Response method. > > The email is as follows: > ----------------------------- > I just wanted to give you a follow up on what I've found in case you run > into the same problem. I placed one of my clients accounts into test mode > and then tried to purchase using a 2-digit month on the credit card. All > those tests would fail, however with a single-digit exp month, the test > would pass. I had added a convertchars around the exp month to convert them > to 2 digits per A/N tech: > > from to > 1 01 > 2 02 > 3 03 > 4 04 > 5 05 > 6 06 > 7 07 > 8 08 > 9 09 > 10 10 > 11 11 > 12 12 > > If I removed this convertchars, all 2 digit months would now PASS and single > digit months would FAIL. If I enabled this convertchars, the opposite > became true. So, with a simple showif, I now either use the convertchars or > I don't: > > [showif [expmonth]<10] > db=monthconv.db][expmonth][/convertchars][expyear]> > [/showif] > [showif [expmonth]>9] > > [/showif] > > All tests thereafter worked. > > My expyear has remained in the 4 digit format. > > ---------------------- > > I'll report back if this turns out to be incorrect, but in test mode, this > seems to be a fix for a problem that I have noticed, but have not seen > reported on this list. > > GK --------------------------------------------------------------------- Clint Davis Webmaster / Interactive Media Specialist Gray Loon Marketing Group, Inc. http://www.grayloon.com 204 Main Street | Evansville, IN 47708 | Phone:812-422-9999 --------------------------------------------------------------------- ------------------------------------------------------------- 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:
This can be easily resolved by putting the expiration months/years into pulldown menus. It has been my experience that visitors/customers will enter all types of crazy things into text fields. So, I try to use radio buttons, checkboxes, and pulldown menus as much as possible in my forms as well as using javascript validation on the text fields.I've always said: If you give a web user the ability to screw up form field, THEY WILL! On 12/20/02 5:20 PM, Gary Krockover wrote:> Folks, > > The following is a copy of an email that I sent to Terry Wilson, who's a > list member that has provided much help on the A/N issue(s). I found that a > client of mine was receiving about 30% failure rate on orders, all with the > error of Expiration date invalid. The other 70% of the orders were > passing fine. This is using A/N and the ADC Relay Response method. > > The email is as follows: > ----------------------------- > I just wanted to give you a follow up on what I've found in case you run > into the same problem. I placed one of my clients accounts into test mode > and then tried to purchase using a 2-digit month on the credit card. All > those tests would fail, however with a single-digit exp month, the test > would pass. I had added a convertchars around the exp month to convert them > to 2 digits per A/N tech: > > from to > 1 01 > 2 02 > 3 03 > 4 04 > 5 05 > 6 06 > 7 07 > 8 08 > 9 09 > 10 10 > 11 11 > 12 12 > > If I removed this convertchars, all 2 digit months would now PASS and single > digit months would FAIL. If I enabled this convertchars, the opposite > became true. So, with a simple showif, I now either use the convertchars or > I don't: > > [showif [expmonth]<10] > db=monthconv.db][expmonth][/convertchars][expyear]> > [/showif] > [showif [expmonth]>9] > > [/showif] > > All tests thereafter worked. > > My expyear has remained in the 4 digit format. > > ---------------------- > > I'll report back if this turns out to be incorrect, but in test mode, this > seems to be a fix for a problem that I have noticed, but have not seen > reported on this list. > > GK --------------------------------------------------------------------- Clint Davis Webmaster / Interactive Media Specialist Gray Loon Marketing Group, Inc. http://www.grayloon.com 204 Main Street | Evansville, IN 47708 | Phone:812-422-9999 --------------------------------------------------------------------- ------------------------------------------------------------- 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/
Clint Davis
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...