Q: Aborting CONSTRUCT statement

Hello INFORMIX experts, here's an exotic problem with an old INFORMIX release (Rapid Development System plus Standard Engine, version 4.0). We run an extensive database application on SCO ODT 3.0. After some changes to the program, there occurred an error at a location that definitely should not have been affected by these changes: a CONSTRUCT BY NAME statement with explicitly listed table columns suddenly (and repeatedly) produced the error message -1108 ('Record not in form'). However, all table columns listed in this CONSTRUCT statement also occurred in the respective screen form. Detailled tests showed that the CONSTRUCT statement in this situation could cope with up to 15 individually listed columns, while adding the 16th would result in the above error message. Surprisingly, the CONSTRUCT statement did not abort when a call to an empty function was placed directly before the CONSTRUCT statement. Neither did it abort when CONSTRUCT BY NAME was replaced by CONSTRUCT ... ON ... FROM ... It was not possible to reproduce the effect of the aborting CONSTRUCT statement in a smaller program. The error seems to occur under very special circumstances only, and I have no idea what they may be. We tried running the version 4.0 compiled program under version 4.1, which also resulted in an abort. Compiling and running the program under version 4.1 did work, however. Yet there is no guarantee that version 4.1 really fixed that bug. Thus I'd really like to KNOW what is going on here. If anyone can help me, please let me know. Birgit Scherbaum bscherbaum@telenet.de