• Im seeing the same thing, over and over again. Some where on microsoft site I seen that it was an issue with SQL Server 7.0 and the possibility that Service Pack 1 had fixed it.

    H.