Nope, that doesn't work either. TABLEUPDATE() just doesn't work for Optimistic Table Buffering anymore, no matter what combination I try. The current row gets updated, I then SKIP to the next Row, and GETFLDSTATE() shows that there are still uncommitted changes, and sure enough, when I REQUERY() I get an error message as such. Uncommitted Changes. But I cannot commit all rows. My connection works fine, REQUERY() and other Remote View functions all seem to work fine. I guess scrap MSSQL7, hate to go back, because it's got a great new interface much better than SQL 6.5


>Hi Brian:
> Just a thought, try TABLEUPDATE(2, .T., {Alias}, cErrorArray). The documentaion states that VFP will attempt to commit all records even if an error occurs. With the 1 parameter VFP stops processing as soon as an error is encountered. Perhaps VFP is simply not reporting an error. Setting the first parameter to 2 would eliminate this possibility. You could also examine cErrorArray after the call, just in case it contains more information.
>
>Hope this helps,
>Ned
>
>To quote another member: "Free Advice worth at least what you paid."