I'm not saying that programming questions aren't important, but I'd spend more time worrying about the business side of the job you're hiring for.
Do you know what the company does? Do you know what they want you to do? Can you do it? Can you do it in a way that makes the company money? Are you going to get along with other people on the team, so that the hiring manager doesn't have to waste his time dealing with personnel problems?
Technical competence is important in an interview, sure, but what's going to put you ahead of everyone else is making the interviewer (who I hope is the hiring manager) know that you're going to play ball and be part of the team.
Another way to show that you are a competent programmer, which is most of why there are programming questions, is to bring in a portfolio of your work. Bring in source code that you've worked on in the past. Ultimately, programming interview questions are auditions where you perform stunts, but showing a portfolio of code you've worked on in the past will show that you can actually do the work that needs to be done.
This is a big hot-button topic of mine, since I'm writing a book about job hunting for techies. See my website at theworkinggeek.com.