Assuming there are no cross app relationships the first thing I would do is make a copy of your application and test everything on that copy before taking a chance on your live data.
I presume that you can use Excel to create Excel sheet with the the Record ID number field and the value for a new field called [RLID]. You could choose to override the actual ID field but he will probably feel more comfortable with a brand new field.
I would change the Key field of the table back to Record ID#. Yes you will get that pop-up warning but in fact what will happen is that QuickBase will update all the records in child tables to keep them connected to that parent table where the key field was just changed.
Then you should be able to do an Excel upload of the Record ID number field and the value for a new field called [RLID]. You could choose to override the existing ID field but you will probably feel more comfortable with a brand new field, thus preserving, at least initially, the old ID field.
Next you will change the key field back to RLID, and once again except all the warnings and Quickbase will once again link every thing up for those child records affected by the Key field change of the parent.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
