Identity field doesn't increment using .NET application (in development)

Hello.

This one kills me!

I am building a .NET application that for managing a database (SQL Server Express 2005).
In my database I have several tables, two of which (for the sake of presenting the problem) are "Patients" and "Therapists".
Both tables are built similarly; There is a PatientSID (PK, int, not null) and a TherapistSID (PK, int, not null); Both are defined as Identity, with an Identity seed of 1, and an Identity Increment of 1.

In my application, I have two forms: (you guessed right...) "Patients" and "Therapists".
On the forms I'm using auto-generated Navigation Bars (made by dragging the accordant table from the Data Source Explorer window to its form), for retrieving, adding, editing and deleting data in my database.
The two forms, like the two tables in the database, were built the same (more then once, I must say...)!!

Now, the problem:
When trying to add a record to the "Patients" form (by using the "Add" and "Save" buttons on the Navigation Bar), the record is being added to the "Patients" table just fine.
For some reason, when trying to add a record to the "Therapists" table, using the "Therapists" form (again by using the "Add" and "Save" buttons on the Navigation Bar), the record is not being added, because the "TherapistSID" is not incrementing, and I get an error message, saying that the "TherapistSID" doesn't allow NULLs.

The code running (and failing...) for the action of saving the new added record is:

Private Sub TherapistsBindingNavigatorSaveItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles        TherapistsBindingNavigatorSaveItem.Click

        Me.Validate()
        Me.TherapistsBindingSource.EndEdit()                                                              ' This is where it fails!
        Me.TherapistsTableAdapter.Update(Me.HW1DataSet.Therapists)

End Sub

For the "Patients", the code is identical.

BTW, When adding a record directly into the table, in the SQL Server environment, it works just fine!
What's going on??

Please help.
Lior.
liorim2Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guy Hengel [angelIII / a3]Billing EngineerCommented:
all you posted looks fine. however, there must be a small configuration problem, so that the controls do not "know" about the PK field to be of type identity
for example, just make sure you look at the right database...
0
liorim2Author Commented:
what "controls" do not "know" about the PK field to be.........?
do you mean, controls in my application?
let me remind what i wrote in my first post: "BTW, When adding a record directly into the table, in the SQL Server environment, it works just fine!".

Lior.
0
Guy Hengel [angelIII / a3]Billing EngineerCommented:
I speak about the navigator bar?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
liorim2Author Commented:
Bugs, Bugs, Bugs...
Well, the problem was with the RecordSet. After killing it and rebuilding it, the problem is gone.
Thanks anyway, AngelIII, for trying.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.