Dave,
The problem here is that ReceiveMail is no longer a column of the Links table, it has moved to the Users table. The warning is generated because you have ReceiveMail has a non-standard table in the new Links SQL, but it is standard in the old Links SQL.
The script checks for any non-standard tables in the new database which are not in the old one, and it comes across "ReceiveMail", which is not standard, and so it looks at the old Links SQL's fields to see if a non standard field named "ReceiveMail" exists. Since ReceiveMail is standard, the check fails, generates a warning, and since you have critical warnings enabled, it becomes a critical error.
Simply dropping the ReceiveMail field from the new Links SQL table should correct the warning.
Jason Rhinelander
Gossamer Threads
The problem here is that ReceiveMail is no longer a column of the Links table, it has moved to the Users table. The warning is generated because you have ReceiveMail has a non-standard table in the new Links SQL, but it is standard in the old Links SQL.
The script checks for any non-standard tables in the new database which are not in the old one, and it comes across "ReceiveMail", which is not standard, and so it looks at the old Links SQL's fields to see if a non standard field named "ReceiveMail" exists. Since ReceiveMail is standard, the check fails, generates a warning, and since you have critical warnings enabled, it becomes a critical error.
Simply dropping the ReceiveMail field from the new Links SQL table should correct the warning.
Jason Rhinelander
Gossamer Threads
