insufficient key column information for updating or refreshing - with my view, why???????

With this view when I try to update it I am having this message: insufficient key column information for updating or refreshing

The table CADUSO  is another view and the table that I want to update is AGENDA_USO_CONEX, Below you can see their structure

CREATE VIEW dbo.AGENDA_CONEXAO_USO
AS
SELECT     dbo.CADUSO.RH_FUNC_NOME, dbo.AGENDA_USO_CONEX.AG_CODUSO, dbo.AGENDA_USO_CONEX.AG_CODCONEX,
                      dbo.AGENDA_CONEXAO.AG_EMPRESA, dbo.AGENDA_USO_CONEX.AG_ID, dbo.AGENDA_CONEXAO.AG_CONEXAO,
                      dbo.AGENDA_CONEXAO.AG_ID AS Expr1, dbo.CADUSO.RH_FUNC_ID
FROM         dbo.AGENDA_USO_CONEX WITH (nolock) LEFT OUTER JOIN
                      dbo.AGENDA_CONEXAO ON dbo.AGENDA_USO_CONEX.AG_CODCONEX = dbo.AGENDA_CONEXAO.AG_ID LEFT OUTER JOIN
                      dbo.CADUSO WITH (nolock) ON dbo.AGENDA_USO_CONEX.AG_CODUSO = dbo.CADUSO.RH_FUNC_ID

-------------------------------------------------------------------

CREATE TABLE [dbo].[AGENDA_CONEXAO] (
      [AG_ID] [int] IDENTITY (1, 1) NOT NULL ,
      [AG_CONEXAO] [varchar] (5000) COLLATE Latin1_General_CI_AS NULL ,
      [AG_EMPRESA] [varchar] (20) COLLATE Latin1_General_CI_AS NULL
) ON [PRIMARY]
GO

ALTER TABLE [dbo].[AGENDA_CONEXAO] WITH NOCHECK ADD
      CONSTRAINT [PK_AGENDA_CONEXAO] PRIMARY KEY  CLUSTERED
      (
            [AG_ID]
      )  ON [PRIMARY]



CREATE TABLE [dbo].[AGENDA_USO_CONEX] (
      [AG_ID] [int] IDENTITY (1, 1) NOT NULL ,
      [AG_CODUSO] [int] NULL ,
      [AG_CODCONEX] [int] NULL
) ON [PRIMARY]
GO

ALTER TABLE [dbo].[AGENDA_USO_CONEX] WITH NOCHECK ADD
      CONSTRAINT [PK_AGENDA_USO_CONEX] PRIMARY KEY  CLUSTERED
      (
            [AG_ID]
      )  ON [PRIMARY]
GO
LVL 1
hidrauAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

LowfatspreadCommented:
because the view doesn't implement a 1:1 realtionship ...

so update the base table directly.  
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SireesCommented:
0
hidrauAuthor Commented:
I noticed that If I have only one table joined to my main table it works fine. This error is a bug so?
0
Anthony PerkinsCommented:
>>This error is a bug so?<<
I am afraid not.  See Lowfatspread's response.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.