The Thor way (who needs fine tools if you have Mjölnir) of doing this is to double each field in your view and update doubled field with table value if changed. More elegant would be a second cursor of changed records linked via set relation plus a function returning changed field names or empty string...

>But I am looking to show them changes made in the underlying table. If I really really did not want to move the record pointer in the table (I am thinking now), I would have to a) run a new query of the same records against the table to get the values from the table again and then b) run a query against the view to get the current values there (using the phrase "WITH (BUFFERING = .T.)" to get the latest changes to the view
>
>and then compare them; this allows me to not move the record pointer in the view/grid.
>
>If I *did* detect the change, the code would still have to find the records with differences in the grid and set some flag on the view there that could then be used to show that the view is out of date with the table (for changes made by another).