> BTW, you might want to check the Mixed up cache, there is an SQL error on > that page. Nobody's prefect. ;-) It was an error caused by any cache with quote markes in it.... all fixed. Thanks for the bug report. Brian Cluff Team Snaptek