Programatically adding a new or updating a record

[RichardBott]

Hi fellow Access users,

In Access XP, when the user is filling out the fields for a new record on a form, one of the options I have is to go to a child form to fill out some detail there. My experience with Access shows that this new 'child' form only works well if the parent form has added the new record before work is done on the child form. Is this experience shared by others?

Given that it is, can I can programmatically open the recordset as was suggested to me last year, and examine the .acNewRecord property to determine whether to add a new or update an existing record?

Thanks for any help you can give.

Richard

 

[TheAceMan1]

How are ya RichardBott . . . . .

[blue] . . . [purple]this new 'child' form only works well if the parent form has added the new record before work is done on the child form.[/purple] Is this experience shared by others?[/blue]

Yes . . . all of us! It has to do with [blue]relationships between tables[/blue]. The rule is:

[blue]You can't save a record in a Child Table, without a corresponding record in the Parent Table.[/blue]

Now . . . I don't know which event your using, but for say . . . a command button, it would be something like this:

[blue]   Dim Msg As String, Style As Integer, Title As String
   Dim NL As String, DL As String, flg As Boolean
   
   NL = vbNewLine
   DL = NL & NL
   flg = True
   
   If Me.NewRecord Then
      Msg = "You have entered a new Parent record!" & DL & _
            "You can't save a child unless the Parent is saved!" & DL & _
            "Click 'Yes' to save the Parent and continue." & DL & _
            "Click 'No' to cancel and abort . . ."
      Style = vbInformation + vbYesNo
      Title = "New Record Detected! . . ."
      
      If MsgBox(Msg, Style, Title) = vbYes Then
         DoCmd.RunCommand [b]acCmdSaveRecord[/b]
      Else
         flg = False
      End If
   
   End If
   
   If flg Then DoCmd.OpenForm "[purple][b]YourFormName[/b][/purple]"[/blue]

See Ya! . . . . . .

 

[RichardBott]

Hi TheAceMan1 and thanks for the info! I shall use the "If Me.NewRecord Then..." construct to prompt the user to save the new record.

Thanks again,
Richard