Hello Mike:

An update on what I have found:

I have the problem on both Desktop SQL 7 and Server SQL 7, with and without SQL Server Pack 1

My BatchUpdateCount in my view is 10.
If I recreate the view with a BatchUpdateCount of 1, the problem goes away.
So, I guess I'll just redo all of my views.
Keep in mind that I did not have this with SQL 6.5.

My other properties of the view are as follows:

=DBSetProp(lcview, 'View', 'UpdateType', 1)
=DBSetProp(lcview, 'View', 'WhereType', 3)
=DBSetProp(lcview, 'View', 'FetchMemo', .T.)
=DBSetProp(lcview, 'View', 'SendUpdates', .T.)
=DBSetProp(lcview, 'View', 'UseMemoSize', 255)
=DBSetProp(lcview, 'View', 'FetchSize', -1)
=DBSetProp(lcview, 'View', 'MaxRecords', -1)
=DBSetProp(lcview, 'View', 'Tables', lctables)
=DBSetProp(lcview, 'View', 'Prepared', .F.)
=DBSetProp(lcview, 'View', 'CompareMemo', .T.)
=DBSetProp(lcview, 'View', 'FetchAsNeeded', .F.)
=DBSetProp(lcview, 'View', 'ShareConnection', .T.)

Also, remember that the tableupdate returns .T.
The SQL Server is updated correctly.

Rick


>>GETNEXTMODIFIED returns 2
>
>A non-zero value means that you've got pending changes on that row. Either your changes are not being written out or something else is making a change after that TABLEUPDATE(). Use GETFLDSTATE(-1) on row 2 to find out what column has been changed. Maybe that will lead you to the problem.
>
>-Mike