NewEra 3.1: Several problems

Hi NewEra folks, Next are some problems I came across when using NewEra 3.1 TC1. I would like the people who read this message to give relevant response (acknowledge, agree, disagree). Here they come: 1. NULL object in executable result in unusefull message If during execution of an executable (.exe) a NULL-object is encountered, a message is issued with the following format: "Exception <magic-number> occurred in <exe-name> at address <address>" When using Pcode however, a message is produced containing errornumber (-1392), modulename and linenumber. This will allow you to find the error very quick. The unusefull message from the executable is already there since the first release of NewEra 3. 2. DataState of superField influences the outcome of ixSuperField::isPrimaryKey() If the dataState property of a superField is set to readOnlyState or disabledState and the primaryKey property is set to TRUE, then ixSuperField::isPrimaryKey() always results FALSE. I think this is not correct because visual properties (eg. dataState) may never influence non-visual properties (eg. primaryKey) 3. Edit-operation in readOnly superField causes ixSuperTable::lockRow() If an edit-operation (eg. CTRL-C or CTRL-X) is performed on a superField with dataState = readOnlyState and the lockMode of the superTable is pessimisticLock, a ixSuperTable::lockRow() is performed. After this there is a locked db-row but the changeFlag of the corresponding row in the dataSet has a value of isOriginal. What's going on here? If a superField is readOnly, the contents of the superField-cell can never be changed interactively and hence can never cause a row te be locked. -- +----------------------------------------------------------+ | Henk van der Geld CASA Volkshuisvesting BV Netherlands | | Phone : (31) 36 539 19 64 | | Fax : (31) 36 539 19 61 | | Email : development@casavhv.nl | +----------------------------------------------------------+