Hi,
Is there any particular reason you want to use code instead of an append
query?
Here is an example of using an append query:
Private Sub YourButtonName_Click()
DoCmd.SetWarnings False ' Disable Access Warnings
DoCmd.OpenQuery "qryAPersonIDtotblMembers"
DoCmd.SetWarnings True ' Enable Access Warnings
DoCmd.OpenForm "YourFormName"
DoCmd.GoToRecord , , acLast
End Sub
Regards,
Hunter57
> Hi all
> I am trying to add a new record from the a parent form to child form, but
[quoted text clipped - 14 lines]
> Please help
> Thanks
Tony Toews [MVP] - 21 Jul 2007 00:25 GMT
>Here is an example of using an append query:
>
[quoted text clipped - 8 lines]
>
>End Sub
You are strongly urged to use error handling, although I do realize
this is sample code.
I prefer, if DAO, to use Currentdb.Execute strSQL,dbfailonerror
command instead of docmd.runsql. For ADO use
CurrentProject.Connection.Execute strCommand, lngRecordsAffected,
adCmdText
If you're going to use docmd.setwarnings make very sure you put the
True statement in any error handling code as well. Otherwise weird
things may happen later on especially while you are working on the
app. For example you will no longer get the "Do you wish to save your
changes" message if you close an object. This may mean that unwanted
changes, deletions or additions will be saved to your MDB.
Also performance can be significantly different between the two
methods. One posting stated currentdb.execute took two seconds while
docmd.runsql took eight seconds. As always YMMV.
Tony

Signature
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/