Glad you were able to get it working. It would have been ok to chop out that part of the script and use SQL 2000, the only side affect would be if we updated a default validation expression for an existing feature, it would not get the update. Its very rare that we change one anyway so its a minor issue. What I need to do to really fix this for SQL 2000 is to re-write that sql fragment in a way that is compatible with SQL 2000. It will require some ugly business like using a cursor, but I think it can be fixed so its still compatible. When I get a chance I will look into this.