quote: well guys, it worked well, thanks again. Gonna have to go back and revise that Level deal at some point though
Glad it worked .
It is not mandatory for you to revise the Level thing. There is always a way to avoid the problem - instead of using just Level you can your Course.Level (it's a field from the Course table, right?). Like that it will never give problems. Also I found that it only gives you the error message when you use it in the SELECT clause. If you use in a WHERE, for example, it causes no problems whatsoever.
In conclusion, I think you may get fine without using that as long as you take that small precaution when using it in the SELECT clause.