Run-time error 2465

[EJO]

TIA!
(sory--originally posted in MS Access forms group, but no responses...)

Error txt:

DB can't find the field 'field1' referred to in your expression.

(A2k running on winxp and win2000)The field does exist, is not
calculated in any way, will compile and once compiled, the error never
again rears its ugly head...

*********************************
Private Sub Form_Current()

Dim ctl As Control

If Me.field1 = "0000.0" Then
For Each ctl In Me.Controls
If ctl.ControlType = acTextBox Or ctl.ControlType = acComboBox
Then
Controls(ctl.Name).Locked = True
End If
Next ctl
ElseIf Me.Field1 <> "0000.0" Then
For Each ctl In Me.Controls
If ctl.ControlType = acTextBox Or ctl.ControlType = acComboBox
Then
Controls(ctl.Name).Locked = False
End If
Next ctl
End If

Me.Lookup1.Locked = False
Me.Lookup1.Enabled = True
Me.date5_Act.Locked = True
Me.date4_Act.Locked = True
Me.date3_Act.Locked = True
Me.date2_Act.Locked = True
Me.date1_Act.Locked = True

If IsNull(Me.date5_Act) = True Then
Me.Completedate5.Visible = True
Me.label74.Visible = False
ElseIf IsNull(Me.date5_Act) = False Then
Me.Completedate5.Visible = False
Me.label74.Visible = True
End If

If IsNull(Me.date4_Act) = True Then
Me.Completedate4.Visible = True
Me.Label73.Visible = False
ElseIf IsNull(Me.date4_Act) = False Then
Me.Completedate4.Visible = False
Me.Label73.Visible = True
End If

If IsNull(Me.date3_Act) = True Then
Me.Completedate3.Visible = True
Me.Label72.Visible = False
ElseIf IsNull(Me.date3_Act) = False Then
Me.Completedate3.Visible = False
Me.Label72.Visible = True
End If

If IsNull(Me.date2_Act) = True Then
Me.Completedate2.Visible = True
Me.Label71.Visible = False
ElseIf IsNull(Me.date2_Act) = False Then
Me.Completedate2.Visible = False
Me.Label71.Visible = True
End If

If IsNull(Me.date1_Act) = True Then
Me.CompleteDate1.Visible = True
Me.Label70.Visible = False
ElseIf IsNull(Me.date1_Act) = False Then
Me.CompleteDate1.Visible = False
Me.Label70.Visible = True
End If

End Sub
**************************************************
Thanks,

Eric

[BillCo]

I dont understand, is the problem coming back again after compiling?

Not recognising an object can be a sign of a mis-matching binary
(compiled) code. this can happen if you make changes in break mode,
save without compile, or other wrong combinations of saving, editing,
not compilng, run-time edits etc. Try making a backup, doing a
decompile to purge any old compiled code, recompiling and running a
compact and repair.

If you suspect that there is a corruption in the module then try this:
make a text copy of the module. Open the form and set "has module" to
no and save. create a copy of the form, set has module to "yes" and
copy the text of the old module into it. delete the old form. compile
and compact.

[EJO]

The original post says "..will compile and once compiled, the error
never again rears its ugly head... "

When I get back in the office I'll try copying the form with the module
and go from there...thnx again!

[BillCo]

If the problem went away after compiling then where is the problem? Is
there a specific action that causes it to return? ...that's where I was
going with the decompile suggestion.

Let us know how it goes!