Hi John.

>> Ahhh.... You suggested a solution that did not work because you did not test it. Yep, I have been bit by this myself. Since then, I resolved that if I was going to post a line of code, I needed to test it. Why? Because I know I have this figurative target on my back and that somebody is going to test it and further, will take delight in citing that the code did not work. <<

I generally try to test any code that I post because I think that it is a hinderance rather than a help to the questioner if I post something that is half-baked and doesn't work.

Having said this, I am sometimes have an idea that I think might work, but do not have time to test it (You know, things like paying work get in the way < g >). In which case I may still go ahead and post it along with a disclaimer that says 'This is off the top of my head and untested but...'.

I don't know if the issue here is the target on your back or the expectation that code posted by an expert in the field will work unless explicitly stated otherwise.

Just mu $.02 ;-)

Marcia