>>* Props for the LV_MASTER2.key1 field.
>>DBSetProp('LV_MASTER2.key1', 'Field', 'KeyField', .T.)
>>DBSetProp('LV_MASTER2.key1', 'Field', 'Updatable', .F.)
>>DBSetProp('LV_MASTER2.key1', 'Field', 'UpdateName', 'master2.uid')
>>DBSetProp('LV_MASTER2.key1', 'Field', 'DataType', "I")
>>
>>When you do joins and getting the proper key to control the update for one of the tables gets tricky.
>>
>>To me this is a standard that is well worth upholding.
>
>I haven't dealth with very complex scenarios as far as views go, still I've faced the problem to a certain level, but you're right, making PK names unique across the database seems like a good idea, I'm still not too sure about the other non-key fields.

I will always put my key, and foreign keys in a way to not allow duplicates.

As a standard this is far more important to uphold than variable naming add ons.

Your data is exposed to the world, your code is usually not.

__Stephen