Updating SQL Express With Bound Controls Problem.

I'm using VB.NET on VS 2005 with SQL 2005 Express. I have one master table with two child tables related with a FK. The master table in the SQL 2005 database has an Identity Column set up as the primary key with Increment as "1" and Seed as "1001". Each child table in the database has one Identity Column set as a primary key also with Increment = 1 Seed = 1001. Each child table also has a column set as a foreign key to the master primary key. The typed dataset was created in Designer and the table adapters, bindingsources, bindingnavigator and DGVs were created by dropping the tables on the form. I added some code for each child table in the bindingsource button save event for the two additional child tables:
' my added code
child1BindingSource.EndEdit
childT1ableAdapter.Update(ds.Child1Table)

child2BindingSource.EndEdit
child2TableAdapter.Update(ds.Child2Table)

Now the trouble. I changed the dataset (not the actual database) columns for each table's PK to AutoIncrement with Seed "-1" and Step "-1" to allow the client to create new records that do NOT match an existing key in the backend database. I've read on the forums where this is best pratice to prevent collisions. Please correct me if this is not true. When I create a new record by clicking the "+" button on the binding navigator, I see the "-1" inserted into the correct bound field for the primary key column of the parent table. I can then click into either or both the child DGV empty rows and see that same "-1" value appear in the correct FK column of the DGV. Everything looks good until I try and save the newly added rows were I get the "The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Parent_Child" error. If I change the dataset back to Seed 1, Step 1 then it does not throw an error during save and does save the child data. However the value of the Primary key on the DGV cells displays the value "1001" (or the next auto incrementing value) and NOT "1" which is the seed value for that dataset's table's primary key column. I can change the Seed and Step back to "-1" on the dataset tables and get the error during save or change the dataset table primary key column to Seed 1, Step 1 and the data is saved but with an incorrect identity value. Why does it use the identity value from the database and not the dataset? It seems to me it should work the same no matter what I assign to the autonumber seed value.

I had previously posted this in the Windows Forms forum but with no solution.

Regards,

DeBug