You can easily show and edit records resulting from database views. However, to enable editing of database views and, by implication, their underlying table records, two conditions must be met:
A Virtual Primary Key must be asserted on the database view in Iron Speed Designer. This enables the generated application to uniquely identify a specific virtual record comprised of the underlying tables. The generated application must be able to uniquely identify a record (physical or virtual) in order to edit it, otherwise the application doesn't know which one to edit. (Virtual Primary Keys are available only in Enterprise Edition.)
Editing a database view record must not violate any constraints in the underlying database tables. For example, if the database view omits certain required fields (e.g., not-NULL constraints) in the underlying tables, then the generated application may attempt to edit (update) underlying tables without having all the required fields. This will cause the database to throw an exception when the generated application attempts to update the underlying table records.
Virtual Primary Keys are enabled in the Databases folder of the Application Explorer window in Iron Speed Designer. Alternatively, you may add them from the Properties dialog, Edit Global Properties sub-dialog.