David
Thanks for your reply and apologies for not responding sooner, it's been hectic.
After further investigation we are both correct - kind of ... 🙂
You are correct for people running the "80VP1Upgrade.sql" script against the v8 database on SQL server versions 2005 onwards.
However, we run SQL server 2000 and as such, this script fails to run and fails to create that column.
The reason the "80VP1Upgrade.sql" script fails to run on SQL server 2000 is because :
SQL server 2005 onwards calls the following objects these names :
"sys.objects" and "object_id"
and
SQL Server 2000 calls those objects :
"sysobjects" and "id"
Hence, the supplied "80VP1Upgrade.sql" script in the WFM 4.04 patch runs fine on SQL server 2005 onwards, but fails on SQL server 2000.
We made changes to the line in the script as follows to get it to run on SQL Server 2000.
Original Line:
IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[AMS_ValidationExpression]') AND type in (N'U'))
Edited Line:
IF EXISTS (SELECT * FROM sysobjects WHERE id = OBJECT_ID(N'[dbo].[AMS_ValidationExpression]') AND type in (N'U'))
So, anyone running SQL server 2000 who experienced the error as listed in the 1st post should restore their backed up DataMinorEdit.asp and apply the above fix to run the SQL script and update the DB schema accordingly.
Hope this clears up any confusion.
David, could the 4.04patch mention the above - so people not running SQL 2005 Server onwards will be aware of what action to take ?
Thanks.