>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.
Joe, while it's easier to read a simplified restatement of the problem, sometimes it's the little details that have tripped up the person. Also, you have to remember that what is difficult for you to read, "maxlønn" or "andreprodukt" is as clear to Per as "MaxLength" and "OtherProduct" would be to us (and I'm guessing at the Norwegian, here, folks, please don't be rude if I'm way off).
SELECT statements are particularly apt to have one clause wrong or a parenthesis is the wrong place because they are so complex.
Barbara
