Do you know if that is the case with Visio? That it expect Fkeys to be the same name.

>Jacob,
>
>I've been doing this for about 7 years now with FP/VFP with no problems. The clarity is well worth the small price of typing the extra characters. It is especially helpful in SQL joins and such as it is very clear what table the fields are from and I don't have to type table names.
>
>One PITA I've had is that most CASE tools seem to want to insist (or at least lean toward) having fkeys with the exact same name as the pkey in the parent table. Obviously, this won't work with this naming convention.
>
>Ken
>
>>In my reading I came across a convention for namining fields in a table that used a 2 letter table identifier followd by an underbar as a prefix to all table field names.
>>For example in a Customer table une would finf fields:
>>cu_CustCode
>>cu_Address
>>cu_City
>>cu_State
>>
>>etc. Each table had its fields specified in this manner.
>>
>>It is clear that there are advantages to this nomenclature in that you can easily identify and distinguish a field in a table from memory variable. There are also advantages in SQL statements.
>>
>>Doing it however is somewhat of a pain and I am wondering if it is worth the effort.
>>
>>Does anyone have any experience in using this naming approach?