(Super Natural) Enhance to handle file updates in transactions

In Super Natural we have a large number of files defined. We are constantly updating those file definitions. We add/update/delete fields with new releases of our application. Currently there is no elegant way to get the updates into Super Natural. What I currently have to do is go into Super Natural Maintenance, then individually Modify each file and then save it. This appears to update the definition. This must be done manually for each file. The real problem is that there is no way to get that change into the users transactions. Since there is no cross reference it's virtually impossible to find which transactions are using the affected file. When users call our Help Desk they must take down the transaction information and we typically have to walk the user through a Modify and Save of the transaction. The tool was developed for end users which typically have very little technical skills and the concept of doing a modify/save is confusing for them. We should be able to update the file view and then also find out which transactions use the file. Then execute an option which would update them. This would save countless hours between our users, Help Desk and DBA staff.