New fields added to table migrated from SQL2005 to SQL2008R2 remain NULL after INSERT

We have upgraded from SQL Server 2005 to SQL Server 2008R2. For some reason, when I add a new field to a table on the new server, an insert query will populate every field but the new one, leaving it NULL. I am using a field list along with my values list. All of the detailed column properties are the same as adjacent fields which continue to work fine.

It's interesting to note that an UPDATE query will successfully update the new field after the insert. Also interesting is that, if you create a new table from a script (after adding the new field), the new table doesn't experience this problem, so I'm wondering if it has to do with how the DBs were migrated over to the new server (a process I wasn't involved in)... if some flag or parameter did not set properly on the table after it was brought over, and insert queries are ignoring new fields somehow.