• I believe mine was fixed when I updated both the server and my developement machine to latest SQL 2005 service pack.

    Mitch