Viewpoint Pro Brain-Damaged?

A colleague is getting very frustrated with Viewpoint Pro 2.0. She finds that database changes render useless any related superViews that are defined for the reports that she's developing. Instead of modifying the superViews to correspond to the new database definition, she finds that she needs to delete and rebuild the superViews and recreate her reports. Throwing out completed reports and redeveloping them from the beginning just because of a minor database change is, needless to say, very annoying! A voice at Informix Support has confirmed this behaviour of Viewpoint Pro and the required workaround, but we'd really like them to be wrong. Can anyone suggest a less time consuming process for reflecting database changes in a completed Viewpoint Pro report? Or at least confirm that we have no choice in the matter? Thanks, Dan -- Average behaviour produces average results. Nonconformity is thus necessary (but not sufficient) if you want exceptional results.