Allan,

<< Here is my scenario: The Primary Keys in all of my tables is a GUID.  I
do this to separate the Primary key from the rest of the data.  I want a
unique Value here. So the “WorkCode” value stored in my "Call master” table
really won't reference the appropriate code in the “WorkTab” table. I use
this lookup in Drop down selectors on the Call Master screen.  I have a ton
of these drop downs

So if I’m reading you correctly. I should replace the “Work Code” in the
“Call Master “ table with the Primary Key Value from the “WorkTab” table..
(the GUID) >>

Either that or define a unique key on the column in the WorkTab table that
you wish to use instead of the primary key.  You can use both primary keys
and unique keys as the target of a foreign key relationship.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Allan,

<< Here is my scenario: The Primary Keys in all of my tables is a GUID.  I
do this to separate the Primary key from the rest of the data.  I want a
unique Value here. So the “WorkCode” value stored in my "Call master” table
really won't reference the appropriate code in the “WorkTab” table. I use
this lookup in Drop down selectors on the Call Master screen.  I have a ton
of these drop downs

So if I’m reading you correctly. I should replace the “Work Code” in the
“Call Master “ table with the Primary Key Value from the “WorkTab” table..
(the GUID) >>

Either that or define a unique key on the column in the WorkTab table that
you wish to use instead of the primary key.  You can use both primary keys
and unique keys as the target of a foreign key relationship.

--
Tim Young
Elevate Software
www.elevatesoft.com


Tim;
I'll give that a go

Allan