>I am trouble-shooting someone else's code and something caught my eye. The other programmer, who usually produces great code, specified a SQL VIEW with a column identified as 'KeyField', .T., but there is no TAG for the field in the base table.
>
>I thought a KeyField had to be part of an index expression. Am I wrong?
>
>The base table appears to get updated with no problem on test data and application running on a single machine. However, over the network of about 50 users, I have my doubts.
>
>A second question, is KeyField only specified with .T. when it is part of the primary key expression, or should a field be specified as a KeyField if it is part of any index expression?
>
>Please straighten me out on these two issues!
>
>Your help is appreciated!
>
>Thomas Allan
KeyField means that a SQL WHERE clause will be generated (internally) to find which record to update or delete.
For logical purposes, the key field or fields should be unique.
For efficiency purposes, there should be indices on the fields.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
