This is a new geodatabase still in the dev phase. So changing the key field names is not an issue. I have already done so. So now the primary key in the feature class matches the foreign key field name in the related tables and it is now working correctly.
Thanks for the help!
Maybe it is just me but it seems like this should be explained somewhere. Or did I just miss it?
Travis