Good to know about that foreign key that exists on the EMPS table.  Thanks for the heads up and I'm glad you're working

Hi,
just as information, after downloading the latest version of SF (dated 10-10-2006) the attached sample worked and allowed to create a new record into the EMP table.

Cheers,
Kari

ps. Incase somebody tries the example - add the DEPTNO field to the form. Otherwise you get a referential integrity error from Oracle.

Ben,

thank you very much.

Kari

Well, not really... there were several places within the OracleDataSourceItem that changed in order for it to pass the new unit tests, but what I can do is post a new install here by the end of today.

Great!

Just in case if the update gets delayed, would it be possible to get the "insert"-fix so that I could work on this project during the week-end. Now I'm sort of stuck....

Cheers,

Kari

OK, Kari, there is no sequence created that you can use for inserting records into the Scott.Emp table.  So, I tried to manually assign one and got the same error you did.  I tracked it down and corrected the problem and we will be posting an update before the end of the week with some changes to the activation wizard, so this will be included as well.  Thanks for your patience.

Ben,

attached is a small application that retrieves data from table EMP.
When you retrieve data and update that's fine.
When you insert a new record (use e.g. 1 for EMPNO and Bart for ENAME) then error appears. Autoincrement is set to false.

Cheers,

Kari

Hi,

I have tried both options - that is setting the autoincrement to true and false. No success. I did additional testing using a very simple table from Oracle's SCOTT.EMP using just two columns (EMPNO and ENAME)

As you see - the original error was coming from Oracle but when the autoincrement thing was fixed, then the VB.Net started to give the errors. One more thing, in the debug-window is now SQL-statement for the INSERT.

Would it be possible for you to write a simple application that can be used to enter a row to Oracle's SCOTT.EMP table? Then I could verify that it works in my environment and I could also use that as a reference point whe trying to figure out where it goes wrong. The database version 10g and I'm using VB.Net.

Cheers,

Kari

If you are setting your PrimaryKeyIsAutoIncremented property to False, then you will need to manually specify a primary key for the property.  Also, if you set the PrimaryKeyIsAutoIncremented property to True, then you will need to set the OracleSequenceName property on the business object so the business object knows what sequence to use for the auto-incrementing of the primary key.  It is possible that the OracleSequenceName is nothing and that might be what is throwing the error.  Try setting the sequence and let me know what happens.

What does the structure of your table look like?