FIX: Update Trigger Fails After Upgrading to 4.20K8
  
PSS ID Number: Q102416
Article last modified on 08-16-1995
 
4.20
 
OS/2
 

----------------------------------------------------------------------
The information in this article applies to:
 
  - Microsoft SQL Server version 4.2 for OS/2
----------------------------------------------------------------------
 
BUG# OS/2: 1727 (4.2)
 
SYMPTOMS
========
 
After upgrading to SQL Server version 4.20k8, an update trigger may
fail with the following type of message:
 
   Invalid column name ''.
   (Msg 207, Level 16, State 3).
   Invalid column name ''.
   (Msg 207, Level 16, State 3).
   Invalid column name ''.
   (Msg 207, Level 16, State 3).
 
The column names contain indecipherable characters. This can also
happen if a dump made on a server running a version earlier than
4.20k8 is loaded into a server running 4.20k8.
 
WORKAROUND
==========
 
Drop and recreate the UPDATE trigger to avoid this problem.
 
STATUS
======
 
Microsoft has confirmed this to be a problem in SQL Server version
4.20K8 for OS/2. This problem was corrected in SQL Server version
4.2aK11. For more information, contact your primary support provider.
 
Additional reference words: 4.20 4.2k8 update trigger 207
KBCategory: kbsetup
KBSubcategory: SSrvServer
 
=============================================================================
 
Copyright Microsoft Corporation 1995.
