What have I done wrong!

#10 (**permalink**) 28-Jul-2006, 08:19 AM

Steve on my form should it be a text box or list box?
It is just for showing what I have entered into another form no more than 50
letters...Regards Bob
Should be spelt in Name or Control source window?

"Steve Schapel" wrote in message
news:%23t8FNUPjGHA.3848@TK2MSFTNGP04.phx.gbl...
> Bob,
>
> First two things to check:
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/information-technology/11200-what-have-i-done-wrong.html
> - did you spell the name of the field exactly correctly when put on the
> report?
> - is the report based on a query, rather than directly on the table, in
> which case the field will have to be included in the query?
>
> --
> Steve Schapel, Microsoft Access MVP
>
> Bob wrote:
>> Added a new Field to my Table, Put a text box on the form, all good, then
>> tried to add a text box to the Report linked the that field, But now when
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11200
>> I try to open the Report I get this error
>> Enter parameter Value and below my field BottomTaxLabel
>>
>> Thanks in advance.........Bob Vance

#11 (**permalink**) 28-Jul-2006, 08:19 AM

Bob,

Well, if that is the Record Source of the report, then it sounds like it
must be a Query... unusual to have a query with its name starting with
rpt, but anyway... go to the Queries tab in the Database Window, and see
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11200
if you can find that query listed there. If it is, go to the Design
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11200
view of the query. I would assume that the CompanyInfo table is part of
the query. You will need to include the new field BottomTaxLabel into
the grid, which defines which fields are returned by the query. The
report can't show a textbox bound to a field which doesn't exist in its
record source. Hope that makes sense.

--
Steve Schapel, Microsoft Access MVP

Bob wrote:
> Got it "rptInvoiceModify"
>

#12 (**permalink**) 28-Jul-2006, 08:19 AM

On naming the control the same as the controlsource it is bound to: Don't.
Either don't name the control at all or give it a name similar but not
identical to the controlsource.

If you're never using VBA then this may not matter, but Access is unhappy
when a code reference refers to something on a form, and that something
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11200
could be either a field or a control. Many developers prefix control names
with things like "txt", "cbo", "lbo" to indicate text box, combo box, or
list box respectively. There are many systems Choose one and stick with
it.

But in general, having a control name with the same name as its control
source will eventually bring you grief.

Think in your own mind: If I refer to Me.BottomTaxLabel, am I referring to
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11200
the field within my recordset or the control on my form? It matters. The
moment you type a character into the control, and until you save the record,
the control and the field hold different values. If you refer to
Me.txtBottomTaxLabel, there is no ambiguity.

#13 (**permalink**) 28-Jul-2006, 08:19 AM

Rick,

Rick Wannall wrote:
> ... but Access is unhappy
> when a code reference refers to something on a form, and that something
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11200
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11200
> could be either a field or a control.

I don't really think this is true.

> Many developers prefix control names
> with things like "txt", "cbo", "lbo" to indicate text box, combo box, or
> list box respectively.

This is correct. On the other hand, many developers do not.

> There are many systems Choose one and stick with it.

Yep. I do. I use this system: "always name a bound control the same as
the field it is bound to". Works for me.

--
Steve Schapel, Microsoft Access MVP