FIX: Updating View Created Using Outer Join Terminates Client
  
PSS ID Number: Q112691
Article last modified on 10-31-1994
 
4.20
 
WINDOWS
 

----------------------------------------------------------------------
The information in this article applies to:
 
  - Microsoft SQL Server version 4.2
----------------------------------------------------------------------
 
BUG# NT: 495 (4.2)
 
SYMPTOMS
========
 
If a view is created by joining two or more tables using outer join, then
issuing an UPDATE on the view may terminate the client process.
 
For example, the following UPDATE command script will cause the problem:
 
   create table testM (m1 varchar(8) null, datam varchar(8) null)
   create table testC (datac varchar(8) null)
   go
   create view testview
   as
   select * from testM, testC where testM.datam =* testC.datac
   go
   insert testC values ("test")
   insert testM values ("hi","testo")
   go
   update testview set m1="help"
   go
 
WORKAROUND
==========
 
You may update the base table directly instead of updating the view.
 
STATUS
======
 
Microsoft has confirmed this to be a problem in Microsoft SQL Server
version 4.2. This problem was corrected in SQL Server version 4.2P33. For
more information, contact your primary support provider.
 
Additional reference words: 4.20 trap nulls Windows NT
KBCategory: kbother
KBSubcategory: SSrvWinNT
 
=============================================================================
 
Copyright Microsoft Corporation 1994.
