The answer is no then.

The quickest way of doing this is :

- create a new report.
- link to the table you want to report on.
- convert it to RDS
- Save it to an XML file.
- Load it in your original file as an XML file.

Or :

- Manually add the new RDS fields.

Given that you'll never add fields to an RDS table unless you're reporting on that field, and you can't a field to a report unless it's been added to an RDS table, then it makes no sense to not have this as a manual step. It's RDS, so you don't need to open those 150+ reports to see if they use the "orders" table. You just need to add the required field to the subset of reports that will need to show the new field.

Is it possible that you're getting errors when reporting because the code to fill the RDS structure isn't smart enough to only update the fields which match between the two tables? If you're filling straight from a record to an RDS record using fieldindex or get_field, then there is a better way of matching fields between RDS and your database.

        Get ComColumnCount sReportID iTable to iMax 
        For iPos from 0 to (iMax-1) 
            Get ComColumnName sReportId iTable iPos to sTmp 
            if (sTmp = sFieldName) move sFieldValue to vData[row][iPos]
This is an example, and not the way I would actually do this. We hold the column names in a dictionary object so we can get the index of it quickly. The example may give you an idea of how it's done. This allows you to only copy fields from the data table to the report table if the field names match. It allows reports to only contain the fields it needs.