Oh, I should have added this: The difference between the VBA stuff you did for Access and what you see here isn't a difference in the VBA language itself; it's in the "objects" that Access and Excel use. It makes sense, really; Access thinks in terms of records, forms and filters, while Excel has cells, rows, columns and worksheet functions. There are many overlapping concepts, but the properties and methods you use for one are different from the other because the applications themselves are different.

If you're not sure what I'm talking about—if you're not sure what properties and methods are—well, neither was I, only a few years ago, and it caused me lots of confusion when I tried to write Excel macros. Once I got it clear in my head, it was fine—better than fine, actually, because object-oriented programming, though different from plain Basic or PL/1 or REXX or what-have you, enables you to do some things much more easily. But knowing the VBA language is only half the battle; to use VBA on Excel you have to get to know the Excel "object model", and when you then have to use it on Access you have to learn the Access object model as a separate task. Knowing Excel doesn't enable you to use Access, and knowing VBA/Excel doesn't enable you to use VBA/Access either—or not fluently, at least.