When I adapt this method to my current project I get an error when doing the append queries on a totally new record on the main form. It works fine if I append to an Item that previously existed.
It says it failed to append the records due to primary key violations. If I save the main record first, then append, it works.
Any idea why this might be happening? I'm guessing I need to start with fresh tables with no data because JHB's example works perfectly.
It happens because the value from ItemID isn't in the table for new created records, (until it is saved).
How do you add/create the records in the subform, click a button or how?
The new records are added as part of the After Update event when the cboItemType combo box is changed.
I forced it to save the record and it works, but I didn't think I should have to do that because your example works without saving the record.
Maybe I can make a working without saving the record, if you post your database with some sample data, (I need the database because it is to much guessing how you've set it up).
In the process of making the database "postable", I cleared out all the irrelevant database objects and deleted all the data.
Then, when I was making some sample records, the append functionality worked fine for the first 2 records. After that, every time I tried to append the records, I got the Primary Key violation error. I solved this by inserting:
Code:
DoCmd.RunCommand acCmdSaveRecord
I posted the database in another thread where we were discussing another problem with the same database.
You can see the code in the After Update event of cboJobType on frmProjectsNew.
If you wouldn't mind taking a look I would be grateful.
The problem rise because of the relationships, you're trying to add records to table tblAccrual, before you've a ProjectId in the table tblProjectList.
So you've done the right thing by saving the record first.
I've put in another way to save it as the DoCmd.RunCommand acCmdSaveRecord command.
