Daymaker, you're making me just a little bit nervous. I am indeed willing to help, but how? I'm firmly against the notion of my simply writing a VBA subroutine for you. Oh, I do that sort of thing professionally, and I've no objection to doing it on that basis; but this forum isn't for that, here we tell each other how for the love of the game.



I can do that—I will—but it would be by helping you understand how to write the VBA module yourself. I don't think it would be very complicated, but you must be the one who writes it because you're the one who has to live with it afterward—explain it if necessary, fix it if the input format changes, enhance it if requested and so forth.

If that's what you meant, great! But if not, reconsider how you want to approach this, knowing that I'll explain forever but you'll have to be the one who actually puts the pieces together into a working whole.

I understand Bob. We're on the same page.

Ok, just making sure. So when you're ready, tell me: How much do you already know about VBA? Have you ever written one, even a very simple one? If so, we can just talk about the logic (and it really won't be complicated). But if not, we should start by introducing you to the, um, the "infrastructure", I suppose it could be called: how to get to the VBA editor, creating a program module and so forth.

Seems I used it once or twice from help on a similar forum; just a copy & paste. That was Excel 2003. I'm on 2010 now and took a look at the attached to where I'm now able to see the VBA through the Developer tab:

http://msdn.microsoft.com/en-us/libr...ice.14%29.aspx

That's pretty much it, sorry to say...