General information
Category:
Databases,Tables, Views, Indexing and SQL syntax
Hi Hilmar, that was the trick, thanks a lot for pointing that out.
This is what's going on: when you check "Key and updatable fields" in the view designer, the SQL statement includes all fields in the WHERE clause to check for conflicts with other users. That means a long SQL statement.
When checking "Key fields only", then SQL only includes a few (or one) field in the WHERE clause to check for conflicts with updates of other users.
This is why I did not have the error when I used tableUpdate(.t., .t.), i.e. forcing all rows, as is almost the same as saying "Key fields only" (conflicts in the primary key are very, very rare).
What I loose using "Key fields only" is the automatic conflict management, which I can do elsewhere. But at least the view is working, and I know why it is working know. Thanks a lot.
Regards,
Javier.
>>Hi Hilmar, with your answer I have two more questions:
>>- Is the SQL statement out of limits with 100 fields? I think VFP limit is of 8 KB per statement, which is a lot
>>- Why does the error go out when I force all rows to be updated?
>
>I don't know the answers. But I still think that you should try "key fields only", to see if that works better.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only