Let's just examine your technical writer's approach to problem solving, shall we? (you don't have to answer that, it was rhetorical)
First post, incomplete code (not in code tags, so you got the 8) smilie) and an incomplete error message.
Second post, still no code ("it's too long" - you could have attached it), but an error message that points exactly to your problem.
Third post
Perhaps if you posted the whole of the details it might get easier, but one-liners are not much help to a novice.
So, you can post incomplete snippets, but we have to provide fully crafted answers?
but I am in no way unfamiliar with forum etiqutte (sic)
Yeah, right.
This isn't about etiquette, it's about common-sense.