Skip to main content

Like Frankenstein, the case of the curious charge from Enterprise is back alive....

A couple of months ago, I wrote about a curious charge of $40 from Enterprise (read the post for background). The gist of it is Enterprise Rental Car stuck me with a fee that they could not substantiate. They claimed I ran a toll while driving one of their cars and that they've:

  • decided to pay the fine for me
  • decided to charge me a 33% "admin fee" for that privilege
  • decided to wait several months before notifying 
  • decided to charge the fine + admin fee to my credit card.
So I did what anyone should: I called them to dispute it. Didn't get anywhere with them so I filed a dispute with American Express. After a couple of disputed charges, Amex ruled in my favor and I thought all was done. Well, guess what? It's not! Apparently, Enterprise really wants their money. So they've
  • decided to send me another notice (with no mention of our prior entanglement)
  • decided to change the fine from $30 to $25 (no reason given)
  • decided to call it a "parking fee" (that's what their customer service rep told me. When I told her that E-ZPass Maryland doesn't do parking, she didn't have a good explanation).
Anyway, I just called up Amex and explained the situation. They cancelled my card and another is in the e-mail. So now that Enterprise can't put unauthorized charges on my credit card, I would like to see what they do next. If it takes going to small claims court...well I have some vacation time saved up.

Yeah I know I've spent way more than $40 (in terms of time) on this case, but it's the principle (not principal) of the matter. 

BTW, someone from Enterprise apparently read my initial blog and got in contact with me. I have contacted him since I got the new letter and he's looking into the issue. So score 1 for their web "social network monitoring" group.

Comments

Popular posts from this blog

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology.

InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options:

convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations)use one of Al Gore's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously. You'll need every bit of time you can get.
quit immediately while you still have your sanityFirst, InfoPath:

To me InfoPath is like programming in assembly language. Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button:

in most technology: buttonA.enabled = false (or something similar).

In InfoPath, you simply can't do this.…

Technical Certifications are worthless

Technical certifications, especially in the IT field, are totally worthless. Why? All a technical certification prove is that you were able to buy a couple of exam prep books, cram them in a week or two and take an exam. My monkey (if I had one) could do that. I can't tell you how many times I have interviewed certification-carrying candidates for open positions at my company only to find them severely lacking in thorough understanding of computer science. I don't care that you have an MSCD or MCP or whatever it's called these days if you don't know foundational concepts in computer science and database design.
For example, I don't want someone who just knows that you store things in a hashtable using keys. I need you to know why a hashtable is better than an array in some cases. I need you to know when an interface is better than an abstract class; when to use recursion; the different kinds of joins and when to use each one; I need you to understand how crucial sou…

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said:
InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... (more)Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A horri…