Thank you, Maclir, and Fastolfe. Mostly, I appreciate the vote of confidence, as I'm sitting here, pulling my hair out. I do have this book, and refer to it (and others) frequently. You probably think that I'm an idiot after that statement, but let me explain. I am a network engineer for a very large ISP/E-business hosting provider. I have never programmed a line of code, prior to about a month ago. Frankly, I prefer net eng work. When I started this contract, I was very honest about what I knew and what I didn't know. And programming was specifically discussed during my interviews. Well, one day, my supervisor cxalls me in his office and says, "Steve, let's test out your programming skills." At this point I'm scratching my head. So, he gave me a spec, and I obsessed on it for a couple of days, and apparently he was impressed. Now, for some reason, I am "tool developer" for my group! My point is, that while I am learning at quite a rapid pace, I'm learning in sort of a fragmented fashion. In other words, I know bits and pieces, thus far. Most of the time, the examples in the Cookbook make sense to me. SOmetimes, they are close to what I need, and I just don't have the knowledge to manipulate the examples to do exactly what I need. Some of the books that I have, have exercises at the end of each chapter, to reinforce what has been taught in the preceding chapter. I wish that I had the luxury of methodically, reading each chapter and doing the exercises. But, unfortunately, since I am learning as I am producing production code, actual programming has to take precedence. I'll say it again; I am deeply indebted to you folks here, who have helped me out.