>>Yes, the older copy flying around often causes this problem. Though in your first reply to me you told that you verified the correct version of a class was used.
>
>Yeah that's a tricky thing though. If you have more than one copy of it you have to be really really careful with all your paths and such. Plus if you have a copy out there you didn't realize you had to begin with...ha..well you get the picture...haha

I had this problem with wrong version of a class being used couple of times myself. Pretty hard to figure out when it's your code, but easy to solve when it's somebody's else :)