Hope that all worked out for you, Mike. And since I promised to update, here is my (similar but not related) issue, in case anyone uses this thread in the future:
Since the beginning of the relationship class in ArcGIS, you could make a relationship class whose name is the same as another table in the database. Though not a best practice, it did work. As of DT 10.3, it doesn't work anymore. The 10.3 client will not be able to see the related tables. Esri has logged a bug for this which doesn't describe the behavior, but rather the fact that the 10.3 client can still see SOME of the tables, when it shouldn't be able to see any of them at all.
Long story short: if you have relationship classes which have the same name as any of your tables, you'll need to rename the rel class to a unique name. I am renaming them in place, without rebuilding them.
Also worth noting: as of DT 10.3, the program will not allow you to create a rel class w/the same name of another table.
BUG-000084853
Inconsistent filtering of related tables, when the table name is identical to the relationship class name.