NewEra 3.0 Question

I have a design issue that I would like to get some feedback on and see how other users have approached the problem. I have a table in our application with many columns that cannot all fit on one window. In 4GL, we had the table represented in several screens with no problem: the user could browse through the screens and when he/she was ready to change a record, could choose Change in a ring menu and the selected record would be locked and the user make the changes, then save the changes (thus unlocking the record). I would like to accomplish something similar In NewEra, using the supertable functionality. Thus, I have painted the table over several windows, requiring a supertable per window, all referencing the same table in the database. I'm using pessismistic locking, so the record is locked immediately when the user starts changing a field. This is fine, except the same table is being referenced in all the windows, so when the table is locked in one window, when the user makes changes in another window, the record is already locked, thus causing the obvious problems. It appears that I need to update the changes on each window before the user can move to another window. Has anyone else encountered this situation and how did you deal with it? Thanks for your ideas and help! -- Candy McCall On-Line Computing, Inc. candym@olcinc.com