>Hi Aleksey,
>just to let you know...
>the problem that I mentioned I solved in this way:
>
>Instead of this code in BeforeUpdate event:
>
>IF valorunitario = 0
> MESSAGEBOX( "Valor não pode ser zero")
> RETURN .F.
>ENDIF
>
>I am using this code:
>
>IF valorunitario = 0
> cUpdateInsertCmd = "RAISERROR('Valor nao pode ser zero',16,1)"
>ENDIF
>
>So, I replace the command that VFP will send to SQL, raising the error there. It work if you use ODBC.
>

Hi Ricardo,

I've modified my code to use RAISERROR and I still have the same issue with the grid - the error is shown twice.
There is no difference in behavior between sending RAISERROR to the server and calling ERROR command locally.
What am I missing? How do you suppress extra error message in the grid?


Modified code:

CLOSE DATABASES all
CLEAR
SET MULTILOCKS ON
ON ERROR

CREATE CURSOR foo (f1 I)
INSERT INTO foo values(1)
INSERT INTO foo values(2)
INSERT INTO foo values(3)


LOCAL oCA as CursorAdapter

oCA=CREATEOBJECT("CABeforeUpdateTest")
oCA.DataSourceType="ODBC"
oCA.DataSource=SQLCONNECT("LocalServer")
?oCA.CursorAttach("foo")

* the following lines generate errors (once per line) - 
* ignore those errors
UPDATE foo SET f1=4 WHERE f1=2
SKIP
SKIP 
************************************


LOCAL oForm as Form

oForm=CREATEOBJECT("Form")

oForm.AddObject("oGrid","Grid")
oForm.oGRID.Visible= .T.
oForm.oGrid.RecordSourceType= 1
oForm.oGrid.RecordSource="foo"
oForm.Show(1)


DEFINE CLASS CABeforeUpdateTest AS CursorAdapter
	FUNCTION BeforeUpdate(cFldState, lForce, nUpdateType, cUpdateInsertCmd, cDeleteCmd)
		?PROGRAM()		
		*ERROR "You are not allowed to modify the record!"
		cUpdateInsertCmd="RAISERROR('You are not allowed to modify the record!',16,1)"
		RETURN .F.
	ENDFUNC
ENDDEFINE

Thanks,
Aleksey.