command button

[angie]

I have a form name “proposals” I have a command button that opens up a formcalled “service”
I would like when I click the command button that when theform “service” opens then is will auto fill the fields “Proposal” based onfollowing
Field “optionOne” and field OptionTwo they are both yes/noand I have it set up so that only on can be yes. Each has it own Proposal field . So which ever option is yes that is theproposal that I want to show on the form service under proposal.

IIf me.optionOne = true then
Forms[service]![proposal] = proposalOne
Else
Me.optionsTwo = true then


Forms[service]![proposal]= proposalTwo
End IIF

[pbaldy]

More like

If me.optionOne = true then
  Forms[service]![proposal] = proposalOne
ElseIf Me.optionsTwo = true then
  Forms[service]![proposal]= proposalTwo
End If

[angie]

Do I place this code into the on click in the command button to open the form? if I do that it will delete the on click marco to open the service form.
Thanks

[pbaldy]

You can add a line opening the form before that bit.

[angie]

I added this to the command button to open the form " But I get the error block if without end if
, it highlights the end sub
not sure how to fix


Private Sub Command125_Click()
On Error GoTo Command125_Click_Err
DoCmd.OpenForm "Service Calls From Proposals", acNormal, "", "[CustomerID]=" & [CustomerID], , acNormal
Command125_Click_Exit:
Exit Sub
Command125_Click_Err:
MsgBox Error$
Resume Command125_Click_Exit

If Me.OptionOne = True Then
Form![serviceCallsFromProposals]![Proposal] = ProposalDescripition
Else
If Me.OptionTwo = True Then
Form![serviceCallsFromProposals]![Proposal] = proposalDescripitionTwo
End If


End Sub

[Micron]

A "block" is a section of code that must begin with a specific opening statement and a corresponding closing statement. Another example is
Select Case something
...bunch of code
End Select

You have an un-paired IF. One way to eliminate it is, don't break up the IF's when it's not necessary. Seems not here, but I can't be 100% sure.

If Me.OptionOne = True Then Form![serviceCallsFromProposals]![Proposal] = ProposalDescripition
If Me.OptionTwo = True Then Form![serviceCallsFromProposals]![Proposal] = proposalDescripitionTwo

Or you could check out the ElseIF construct.

EDIT: True is sort of a default for a Boolean value. If Me.OptionTwo Then... is the same as what you wrote.

[pbaldy]

That's not the code I gave you, and belongs immediately after the OpenForm line.

[angie]

Error when I try this, the highlighted shows that it can not find the field.

Private Sub Command125_Click()
DoCmd.OpenForm "Service Calls From Proposals", acNormal, "", "[CustomerID]=" & [CustomerID], , acNormal

If Me.OptionOne = True Then

Form![serviceCallsFromProposals]![Proposal] = ProposalDescripition

ElseIf Me.OptionTwo = True Then
Form![serviceCallsFromProposals]![Proposal] = proposalDescripitionTwo
End If


End Sub

[pbaldy]

The form name has spaces in one line, not in the other.

[angie]

This is still not working....it highlights the 4th line and it is error "cant find the field "serviceCallsProposals"


Private Sub CREATE_SERVICE_CALL_BUTTON_DblClick(Cancel As Integer)
DoCmd.OpenForm "ServiceCallsProposals", acNormal, "", "[CustomerID]=" & [CustomerID], , acNormal
If Me.OptionOne = True Then
Form![serviceCallsProposals]![Proposal] = ProposalDescription
ElseIf Me.OptionTwo = True Then
Form![serviceCallsProposals]![Proposal] = ProposalDescriptionTwo
End If
End Sub

[pbaldy]

It's Forms, not Form. The other line will error too.

[angie]

Thank you pbaldy,,,, that works great
have a wonderful day
Angie

[pbaldy]

Happy to help!

[Micron]

@angie: I had to go back to my post hoping that it was you who dropped the s but it was me. My apologies.
However I am in good company because it's not Forms[ either: Forms[service]![proposal]= proposalTwo

I also see another potential issue in that you can't put a vague reference on one side of a comparison.
This = proposalDescripitionTwo is located where? It either needs the full Forms! reference or Me but I can't tell which because its location is unknown.

[pbaldy]

I never did that! Somebody edited my post and took out the bangs! I was so focused on the If/Then syntax I didn't notice that.

On the vague reference, I wouldn't say "can't", but I would say "shouldn't". Access will allow it and might be able to work out whether it's a variable or field/control on the form. It certainly wouldn't be able to work it out if it was on a different form.