Identity field in the Data Row

bmains · December 17th, 2003, 11:30 AM

Hello,

I originally posted this field elsewhere, but I guess it is more of a ADO.NET question. I have a table that looks like this:

ID int
Name varchar(50)
Description varchar(512) NULL

When I add a new record via ADO.NET code, it looks like this:

Code:

dim objRow as DataRow = objTable.NewRow()

objRow("Name") = strName
objRow("Description") = strDescription
objTable.Rows.Add(objRow)

I assumed that when you get the data source from a stored procedure, that it would establish an identity. However, I guess this means that it doesn't? Anyway, if I were to set up the column to be an identity, how can I get the identity field to start where I left off? Do I not have to establish the AutoIncrementSeed but do establish an AutoIncrementStep of 1?

Thanks,

Brian Mains

planoie · December 17th, 2003, 02:01 PM

When you add the "Identity" property to a column, you typically don't need to make any modifications to have it start off at the right place. If you have 1000 rows (1-1000) the next row added will get identity value of 1001 if you leave all the identity defaults (seed, increment). SQL figures that out for you.

Regarding getting the ID value when you add a row:
I re-read the other thread regarding this topic and I see where the difficulties are. I'm not sure of an immediate solution.

If you have to work with stored procedures, you are going to run into some problems with the ADO interaction. Because you are populating disconnected dataset tables from SPROCs you aren't going to get the "smarts" of the ADO capabilities (which automatically figure out lots of things directly from the table(s)).

If your goal is to be able to add data rows thru a datagrid, you will probably have to modify the datagrid (add row, enter data) then save the record thru a regular SQL call using a SPROC for the insert. Then you rebind the datagrid and your new row will show up as "saved".

I've worked with datagrids, but haven't played with manually adding new rows to the grid control. I don't see why this would be a problem however. You should be able to add a new dataitem to the grid, set the edititemindex to that item's index so that item is in edit mode. Then the update could determine if that's a new item, and make the SQL call accordingly (add new or update).

Peter
------------------------------------------------------
Work smarter, not harder.

bmains · December 17th, 2003, 04:34 PM

Unfortunately, Stored Procedures are required for me in my applications. With that said, what I was thinking my problem was is that I didn't update automatically to the data grid, but now I'm not so sure. However, I did find other people out there with the same problems I'm having, and have found this solution to the problem:

http://www.dotnetjohn.com/articles/articleid27.aspx

Thanks.