Updating from v3 to v4

[Jariten]

We have just upgraded from v3 to v4 of the DOA components.

We have a basic select statement on a single table that is used by the program for data aware components. This functionality worked fine in v3, but with v4, it is failing to insert a string value despite the debug message box stating that the value will be inserted. Since all the columns in the table are NOT NULL, this causes an issue and is giving me a headache trying to work out what is going on!

SQL Statement :
Select
new_vehicle_id, manufacturer_id, model, pre_product, manufacturer_type, rowid
From
NEW_VEHICLE
where
manufacturer_id = :manufacturer_id

Error Msg:
ORA-01400: cannot insert NULL into ("STAR"."NEW_VEHICLE"."PRE_PRODUCT")

on allowing nulls for the above column (a 'Y/N' field), it turns out that the 'Y' ends up in model. Therefore, despite the debug saying the correct string will end up in MODEL, we end up getting the value for PRE_PRODUCT in there instead with PRE_PRODUCT remaining empty.

We have recreated the dataset just in case something had become corrupt. No dice.

Any ideas?

Alex Scott

 

[Marco Kalter]

When you say that "the debug message box" states that all values are non-null, do you mean the message box that is displayed when you set TOracleDataSet.Debug to True? If so, did you make sure that the "PRE_PRODUCT" column is included? If so, can you check if there is a before insert database trigger that might set this value to NULL?

 

[Jariten]

There are no triggers in the schema, The PRE_PRODUCT column is in the SQL statement in the message box and Yes, it is the TOracleDataSet.debug := True;

Hope this helps and thanks for the reply

 

[Marco Kalter]

I'm not sure what could cause this.

Can you use the Oracle Monitor to see what is actually sent to the database when this error occurs? Can you export this information and send it to me?

 

[Jariten]

Email on route