Keep:

You're right on that I haven't made the step from scripting to programming.
When you consider my background in 1-2-3 and QPW it is easy to see why that
would be true, macros in 1-2-3 and QPW at least in early versions where I
began are more scripting than programming. Then, if you couple that with the
fact of my work experience being an accounting person rather than a
programmer, you can see at least in part why I am the way I am.

I continually have to remind myself about Excel in general, to quit thinking
about the methods I used in QPW and just look to solve the problem in Excel,
however it needs to be done.

I am intent on identifying those weaknesses I have with regard to learning
to be an expert in VBA. And, then I am intent on fixing those weaknesses,
because I think that this stuff is cool when I get the results I want. I get
excited when I figure out stuff in spreadsheets to the point I can't sleep
at night thinking what I'm going to do next.

Now that I know more about who you are and that you didn't mean anything
"harsh" I can more readily accept what you have to say.

Maybe Bruce skipped the theory and went straight to the examples. That's
not so strange... he needs HIS workbook translated from QPW to Excel and
he wants results.. NOW!

Good observation again I think. Of course some people learn better by doing
than by reading and studying. I am more of a visual learner than a book
learner. Probably explains why I made so many C's in college , because I
wanted results and not theory. <LOL

Once I'm done with this last major workbook and then once I've gone back and
tried to clean up some of the "functional" code of the first few weeks, then
I'll try and look at others posts on here. I think Bob mentioned on here
that the point of all this was to get each one to where they could start
being a helper of others rather than just coming here for their own
solutions (not his exact words, but the gist I got out of it).

Later,


Bruce