Hi all,

It appears that I am near the end of my first applied framework application.
Everything appears to be working with no errors during compile.

When testing I was able to pull up the form and input information, all of the validation works as it should and the record saved.

The second record would not save because it is trying to pass ID = 0 to ensure that it is a new record. However I do not fully understand where does it increment the primary key information. I checked that Identity Specification > Identity Increment was turned on but now I get the following error when saving from the HRPaidTimeOff.designer.cs

This appears to be a SQL related issue but I am not so sure.
I looked through the book's index to see if I could find IDENTITY_INSERT anywhere but it is not listed. Im flying blind on this one, I could do a dirty hack to get around it, but I would like to have my first implementation of the the framework pure incase I have to reference it (which would be often)


Thanks

Are you passing in an identity number on the insert? Based on the error, it sounds like you're passing in a value for the identity column.

For example, you have a table with 3 columns, the first one being an identity column.

IDENTITY_INSERT is set to off (the default value, I'm assuming).

Doing this:

INSERT INTO table(column1, column2, column3)
VALUES (1, 2, 3)

will generate that error, because SQL Server is expecting to generate the value in column 1 on the insert.

Instead, you'd want to do:

INSERT INTO table(column2, column3)
VALUES (2, 3)

SQL Server would populate column 1 with the next available identity value for that table.

The other option would be to set IDENTITY_INSERT to ON, but that would defeat the purpose of having an identity column, IMO. The only reason I've seen to use IDENTITY_INSERT is when you're preloading rows into a table during installation/setup of an application (though there could be other valid reasons).

If you're using the code straight from the book, all of the tables use the same format for the identity column name - <tablename>Id. I.e., ENTUserAccountId, ENTRoleId, ENTMenuItemId, etc.

Tim

Tim thanks for your input. Based on what you posted that got me thinking about my Stored Procedures for Insert into my table.

Sure enough I found that the Stored Procedure was passing in the Id field. Removed that and now Im working. So it was SQL related so to speak, I will need to correct that in the Code Generator at a later date.

Thanks for the insight.