OpenForm based on combo box in a continuous subform.

[dhowell]

I have a form [Formulas] with a continuous subform [Formulas - Raws].
subform has a combo box called [lot#}

I have a separate form called [COA - Quick Information].
The following code is opening up the [COA - Quick Information] form,
but is not applying the "Where" clause which is based on the combo box
I double click on the subform.
([COA - Quick Information] form opens up blank)

Here is the code.

Private Sub lot__DblClick(Cancel As Integer)
DoCmd.OpenForm "COA - Quick Information", , , "lot =
'[Forms]![Formulas]![Formulas - Raws].[Form]![lot#]'"
End Sub

Any suggestions would be appreciated.
Doug

[Lauren Quantrell]

Rename the field Lot# !!!
Then...
[Lot] = Forms!Formulas.[Formulas - Raws].Form.Lot"

And before it gets any worse, I'd suggest renaming anything that looks
like [Formulas - Raws] to something like FormulasRaws.

There's a lot of info out there on standardized naming conventions

[Allen Browne]

Concatenate the value into the WhereCondition string:
DoCmd.OpenF... , "lot = """ & [lot#] & """"
or drop the extra quotes if Lot# is a Number type field (not a Text type
field:
"lot = " & [lot#]
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

<dh*****@daubert.com> wrote in message
news:11*********************@f14g2000cwb.googlegro ups.com...

I have a form [Formulas] with a continuous subform [Formulas - Raws].
subform has a combo box called [lot#}

I have a separate form called [COA - Quick Information].
The following code is opening up the [COA - Quick Information] form,
but is not applying the "Where" clause which is based on the combo box
I double click on the subform.
([COA - Quick Information] form opens up blank)

Here is the code.

Private Sub lot__DblClick(Cancel As Integer)
DoCmd.OpenForm "COA - Quick Information", , , "lot =
'[Forms]![Formulas]![Formulas - Raws].[Form]![lot#]'"
End Sub

Any suggestions would be appreciated.
Doug

[dhowell]

I know with older versions of Access, there were isssues with field
naming......

I use Access 2003 and was under the impresison that this was no longer
an issue.

Are your points about the naming a REAL issue or just a programmers pet
peeve..........
Doug

[Allen Browne]

If you use a field name that starts with a number or contains a space or
character such as #, you will have to use square brackets around the field
name wherever it occurs, in SQL statements and in VBA code. That's an
annoyance factor for "real programmers."

The field names that will cause you real grief are those that match the name
of a property or reserved word, such as Name or Date. Nearly everything has
a Name property, so when you refer to the Name field on the form Access
confuses it with the name of the form.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

<dh*****@daubert.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...

I know with older versions of Access, there were isssues with field
naming......

I use Access 2003 and was under the impresison that this was no longer
an issue.

Are your points about the naming a REAL issue or just a programmers pet
peeve..........
Doug