Can you explain why you have multiple Staff tables? Typically, best practice is to have a single table that represents one "thing" (like employees / staff).
And, if your Staff information lives in multiple tables, you'll have to create a relationship to each of those tables. My suggestion to avoid this and other issues in the future would be to have a single Staff table in App 1 and then create a Sync table of that Staff table in App 2. Then, you can build in-app relationships to the Sync table, rather than having to build cross-app relationships.
------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quickbase Solution Provider
Atlanta GA
404.800.1702 /
http://datablender.io/------------------------------
