Is *anyone* using Remote Views with MS SQL 7.0?

It appears that I've discovered a bug in VFP with MSSQL 7.0 -- TABLEUPDATE(.T.) does not reflect committed changes to the Server, when used to update multiple rows in a Remote View with table buffering enabled.

With CURSORSETPROP('Buffering') =5, (table buffering enabled), TABLEUPDATE(.T.) should update multiple rows. It still does, and the updates are reflected on the Server. Problem is, VFP Remote View does not recognize that changes are in fact committed, causing the "Uncommitted Changes" error when I attempt to close, or REQUERY() the View. It's also observed that GetFldState(-1) returns '2' for fields which *have* been committed to the Server. It should reflect '1' for all committed columns.

Note that TABLEUPDATE(.T.) returns .T., (multiple row updates are successful). However the VFP Remote View does not reflect these changes, as can be verified with GetFldState(). I have tested with VFP 6.0, and also with VFP 5.0. Both have the same problem with SQL7.

I posted previously, and now believe have isolated the problem as coming from SQL Server 7.0. Everything worked fine until we upgraded MSSQL 6.5 to the new Enterprise Edition of 7. The new SQL Server is much improved with an excellent new interface and many useful tools, BTW. However, it's disappointing that VFP Remote Views don't seem to work, as we use them extensively in our app.

Is *anyone* using Remote Views with SQL 7.0?