My C/S app was running fine in VFP5, updating Remote Views to MSSQL 6.5, using TABLEUPDATE() with Optimistic Table Buffering enabled. I discovered that there seemed to be a limit to the number of rows which would successfully update at once, however. But it worked OK, albeit a bit slow at times while the Server processed the multiple SQL Update statements delivered by VFP in the background.

Unfortunately, we just upgraded. Remember the old days when upgrades were something we looked forward to? New tools, faster apps? These days upgrades with any kind of MS software seem a bug infested mess.

Anyone wanna try this? TABLEUPDATE() now returns .T. However, the changes are NOT committed! CURSORGETPROP("Buffering") =5, however only one Row is updated! The cursor remains on the same row. I can SKIP down a row in my View, then issue TABLEUPDATE(.T.) again. Force it, even. Same result, with Optimistic Table Buffering enabled, all I get is one Row at a time. All other Rows remain uncommitted. Is the problem our new VFP6, or the new MSSQL7, or the new ODBC driver and Connection? Connection works fine otherwise. No Error condition, since TABLEUPDATE(.T.) returns .T.

Thanks in advance, for any suggestions.
Brian Lee
Project Manager
World Access Network, Inc.