DOA 4.01 gives me the 
error (see subject) when attempting to edit at least a dozen records of a particular table using DOA 4.01 but did not with 3.46 (and does not now that I've reinstalled 3.46).
I created a barebones application accessing this table. The barebones application consists only of data aware controls to ensure no manual SQL updates were colliding with the data aware controls. All active users exited the real application which is normally the only application that accesses this table. I connected the session and opened the query in code (the only code in the application) to ensure that I was alone. While using 4.01, the error occurred, but the same records that caused errors when edited became editable after reinstalling 3.46.
The most unusual thing about the table is that it has three BLOB fields, but editing ANY field causes tha error. There are no triggers on the table and only one index, which is UNIQUE on the PHA, YEAR and REC_NUM. There are no aliases in the query...
SELECT ROWID, R.* FROM PHA.REC R
WHERE PHA =
ha AND YEAR=:year AND REC_NUM>0
ORDER BY REC_NUM
The table structure is ...
COLUMN_NAME DATA_TYPE DATA_LENGTH
DETAILS BLOB 4000
RECOMMENDATION BLOB 4000
STATUS BLOB 4000
HASCHILDREN CHAR 1
LIKELIHOOD CHAR 1
RISK CHAR 1
YEAR CHAR 4
DATE_COMPLETE DATE 7
DATE_IMPLEMENT_BY DATE 7
DATE_RESOLUTION_BY DATE 7
DATE_RESOLVE_BY DATE 7
TIME_CREATED DATE 7
TIME_MODIFIED DATE 7
OLDREC NUMBER 22
REC_NUM NUMBER 22
SEVERITY NUMBER 22
AUTHOR VARCHAR2 35
KP VARCHAR2 35
PHA VARCHAR2 10
error (see subject) when attempting to edit at least a dozen records of a particular table using DOA 4.01 but did not with 3.46 (and does not now that I've reinstalled 3.46).I created a barebones application accessing this table. The barebones application consists only of data aware controls to ensure no manual SQL updates were colliding with the data aware controls. All active users exited the real application which is normally the only application that accesses this table. I connected the session and opened the query in code (the only code in the application) to ensure that I was alone. While using 4.01, the error occurred, but the same records that caused errors when edited became editable after reinstalling 3.46.
The most unusual thing about the table is that it has three BLOB fields, but editing ANY field causes tha error. There are no triggers on the table and only one index, which is UNIQUE on the PHA, YEAR and REC_NUM. There are no aliases in the query...
SELECT ROWID, R.* FROM PHA.REC R
WHERE PHA =
ha AND YEAR=:year AND REC_NUM>0ORDER BY REC_NUM
The table structure is ...
COLUMN_NAME DATA_TYPE DATA_LENGTH
DETAILS BLOB 4000
RECOMMENDATION BLOB 4000
STATUS BLOB 4000
HASCHILDREN CHAR 1
LIKELIHOOD CHAR 1
RISK CHAR 1
YEAR CHAR 4
DATE_COMPLETE DATE 7
DATE_IMPLEMENT_BY DATE 7
DATE_RESOLUTION_BY DATE 7
DATE_RESOLVE_BY DATE 7
TIME_CREATED DATE 7
TIME_MODIFIED DATE 7
OLDREC NUMBER 22
REC_NUM NUMBER 22
SEVERITY NUMBER 22
AUTHOR VARCHAR2 35
KP VARCHAR2 35
PHA VARCHAR2 10
