That's true. I really just had to say something other than "Oh, I'm a bonehead.". But sometimes, I'm a bonehead...


Take it easy!

Joe

>I agree with you. I also prefer to see a clear question, eventually simplified.
>
>Still, there is a reason to give the exact code that causes the problem: you have the exact code! :) I mean: when you don't know the solution or why you have the problem, any change in the code sample can change the problem. I saw a lot of situations when the cause of the problem is very clear when you see the exact code, but not when it is "simplified". Etc, etc... I'm sure you got the idea: the bug is in the part that was removed... :)
>
>Also: usually, when I simplify a problem I already got the solution. The same thing happens probably to many other programmers. So, the problem is solved, so, there's no reason to ask a question. And this is one good reason for which you'll not find too many questions like that. :)
>
>Vlad
>
>>andreprodukt1 & andreprodukt...didn't see the '1' at the end of the first cursor name...I thought he was closing the cursor right after he created it...minor complaint: I wish that when examples are shown, people would keep them as simple as possible. Why a long select statement followed by a cryptic filename (or in this case, cursor)? When not , , etc...to make it obvious that we are talking different names. I personally don't have time to go through the logic of a long select statement and be picky about filenames, variable names, etc...I want to look quickly, see if I can help, and move-on...now, you might want to say "Well, if you don't have time to give a question the proper attention, don't get involved", but my point is still valid: Keep it simple and clear. More people will take the time to give it a look and it increases your chances of getting a good answer and it decrease your chances of confusion.
>>
>>Sorry for the confusion.
>>
>>Joe
>>Joe

Joseph C. Kempel
Systems Analyst/Programmer
JNC