Y2K related Fun with my local ISP

greenspun.com : LUSENET : TimeBomb 2000 (Y2000) : One Thread

About two months ago I received email from my ISP asking that I update my account information, as my old credit card was set to expire last month (March). My particular ISP prefers that clients update their information via a secure website, which I accessed at that time. I've been with this ISP since they first started doing business, and so I've dealt with their secured website before.

When I entered my new credit card information, I noticed that their secured webpage for this information was NOT y2k compliant (i.e. it wanted MM/YY for the expiration date as opposed to MM/YYYY), so I entered 00 for the YY.

A little before midnight tonight I received another automated email from my ISP stating that my credit card was about to run out *this* month (April) and that I needed to update my information...again. I went back to the secured website, the form for which is still not y2k compliant, and checked my account information, which was just as I had entered it the first time, with 00 for the YY. I reentered it, and then sent the ISP's accounting section a note telling what I'd done, and asking them what they were doing about their non-compliant forms...

guess we'll see.


-- Arlin H. Adams (ahadams@ix.netcom.com), April 06, 1999


This just goes to show you that the simple expiration dates on credit cards are not just Visa/MC/AMEX problems. There are probably thousands of systems out there that do simple date checking on these mm/yy kind of things.

-- Ken Stauffer (kjs@stauffercom.com), April 06, 1999.

Not to mention millions of spread sheets with YY.

-- Novacop (Sandmann@alasbab.com), April 06, 1999.

So, Arlin, if you're temporarily missing in action next month ... we will know why. If they don't get their act together try getting your service through your local phone service...no credit card info required...billed along with regular phone service.

-- Shelia (Shelia@active-stream.com), April 06, 1999.

Moderation questions? read the FAQ