Address locator with a Feature Class and separate table of addresses?

Discussion created by odoe on May 23, 2011
Latest reply on May 23, 2011 by odoe
I know I have seen something similar to this built before, but I'm not sure how to do it.
I have a Feature Class in SDE or Parcels (polygons) that have unique IDs.
I have a separate table in the SDE with the the address information for each parcel in the Parcel Feature Class (tied by OBJECTID).

I am trying to build a locator that will use the Features to to return results based on the addresses in the related tables.
Reading this page

It would look like I can set the Feature as the Primary table and the Table of addresses as the Alternate table, but I think I'm misunderstanding those roles.

I attached an image of the Create Address Locator I am trying to build with the error it is giving me.
Am I going about this the wrong way? Can I not create an Address Locator in this fashion?

I was kind of hoping there would be a way to do this maybe based on a SDE Relationship.