How does esri relationship classes handle objectID connections?

[MichaelThornton]

I want to use a relationship class GDB object to relate multiple (i.e. two) non-spatial tables (say table name 'Historical Records' and table name 'Recommendations')  to my feature layer. My concern is that if someone deletes a polygon and redraws it on a sde two-way replication connection for that feature layer, new objectIDs will be created on that feature layer and thereby breaking my connections between the non-spatial tables and my feature layer. Does ESRI have a way of handling this?

[George_Thompson]

I would not use ObjectID's as the "joining" field for the relationship class.Relationship class properties—Help | ArcGIS Desktop .

[LorneDmitruk2]

Further to George's reply, ObjectID's should not be used as primary or foreign keys. For establishing relationships you're better off creating and using a GUID or your own primary key field.