Hi
Maybe the TABLEUDATE() and table buffering is the issue here.

>Hi Dorin
>
>>So, with SET DELETED ON...
>>
>>You have a remote viev
>>Delete one record from remote view
>>Update with TABLEUPDATE()
>>SELECT ... from remote view alias
>>
>>The deleted record appear in query?
>>
>>I've done some tests and the deleted record wasn't there
>
>I have a way to find the most typical of problem, ahm!! <g>
>
>I put in a browse on the remote view in this buildtree() method that houses the SELECT statement and yet the deleted record shows in the browse window.
>
>My framework CodeBook as Transactions, will that affect results?
>
>Here below is the Delete() function from CodeBook as it already exists by the original coder
>

PROCEDURE delete
>LOCAL lnRetVal, laError[AERROR_NUMCOLUMNS], lnOldArea
>lnRetVal = FILE_OK
>lnOldArea = SELECT(0)
>
>*-- Delete the current record.
>DELETE
>
>*-- If we are using TABLE buffering, then we assume that the user will
>*-- have the ability to REVERT all deleted records. Therefore, do not
>*-- issue a TABLEUPDATE().
>IF INLIST(CURSORGETPROP("BUFFERING"), DB_BUFOPTRECORD, DB_BUFLOCKRECORD) ;
>		AND !TABLEUPDATE()
>	SELECT (lnOldArea)
>
>	*-- Undo the changes made to the buffer ... the deletion
>	TABLEREVERT()
>
>	*-- Return error number of what went wrong
>	AERROR(laError)
>	lnRetVal = laError[AERROR_ERROR]
>
>ELSE
>	*-- If you are using record buffering or no buffering
>	IF !EOF()
>		*-- Get off of the deleted record
>		SKIP
>
>		IF EOF()
>			*-- If the record you deleted was the last record,
>			*-- reposition yourself on the new last record.
>			SKIP -1
>
>			IF !BOF()
>				*-- Return that the operation was successful.
>				lnRetVal = FILE_OK
>			ELSE
>				*-- If you deleted the last record, indicate so.
>				lnRetVal = FILE_NORECORDS
>			ENDIF
>		ENDIF
>	ENDIF
>ENDIF
>
>SELECT (lnOldArea)
>
>RETURN lnRetVal