I believe Kevin is working on this issue.

The problem has to do with SQL Server trying to insert instead of over writing the value its being fed. It'll work the first time around but then you come back and edit the field it'll bomb, right? If you change your field type to varchar you won't have this problem.

We ran into this during one of our class sessions.