Hi, +1 by reading. (The fix for the SQL injection issue had actually added that property in the first place ... so until then, the code from the other class had been accessing a non-existent property ...) Oliver