Run Time Error 2465 In Report

[desk4tbc]

Hello again guys,



I'm getting a Run-time error 2465 on a piece of code in a report. It works just fine as a form but not in a report. I was wondering if vba was handled differently between the two access objects and if there was a way to refer to data in a field not explicitly shown in the report.

Below is the code:

If [1MC] = True Then chk1MC.Caption = "P"

It refers to a Yes/No field that isn't shown on the report due to the standard checkbox being too small for the purposes here.

Any help would be much appreciated!

[TheShabz]

error 2465 usually means Access can't find something. I assume it's looking for [1MC]. What is that?

Also, your If statements should be closed with an "End If". Not sure if it was omitted from the code snippet or from the original source.

[desk4tbc]

Thanks for the quick reply.

[1MC] is the aforementioned Yes/No field. There isn't a control on the report with the name "1MC" but it is a field within the data source.

Also for the If statement, Access doesn't freak out if its all in one line, but I've added it anyway and it still doesn't work .

[TheShabz]

You mention that it is not shown on the report. How did you bind the report to it's control source? I don't think you can refer to a table/query field that way. Try opening up a recordset on the table/query then reference that. So:

Dim db As DAO.Database
Dim rs As DAO.Recordset
set db = CurrentDB
set rs = db.OpenRecordset("table/query Name", dbOpenDynaset)

If rs![1MS] = True Then
chk1MC.caption = "P"
Else
End If

Set rs = nothing
Set db = nothing

[RuralGuy]

In order to refer to a field in a RecordSource in a Report, the field must be bound to a control on the Report. The Control need not be visible, but it must be there.

[TheShabz]

^^^^^ That too

[desk4tbc]

Thanks guys.

That's what I figured Rural, since the exact same code works fine in a form. I'll go change a few things around.

[RuralGuy]

That has been the case for many revisions as I started with AccessXP and it was there. Glad we could help.

[desk4tbc]

It works now that theres a reference to the field. Very odd behaviour as one object behaves one way while the other behaves contrary to the first. But thanks again for your expert help!

[RuralGuy]

You're welcome. Thanks for posting back with your success.