Solved Error 2448 Can't assign a value to this object

[vanzie]

Hi everyone

My code:

Dim ctrl As Control
For Each ctrl In Detail.Controls
    If (TypeOf ctrl Is TextBox Or TypeOf ctrl Is ComboBox) Then
        ctrl = StrConv(ctrl, vbUpperCase)
    End If
Next

This code is fired upon clicking the Save button in my form and is the first code in the line. All other codes follow after. In all my other forms, this code executes as I want it but in this specific form, it gives me the 2448 error. My form is an unbound form and consists of saving a person's information such as names, address, date of birth etc.

I've checked my table and all fields in the form but I cannot find the fault.

 

[arnelgp]

maybe the control has No Value, so add a blank string:

ctrl = StrConv(ctrl & "", vbUpperCase)

 

[vanzie]

maybe the control has No Value, so add a blank string:

ctrl = StrConv(ctrl & "", vbUpperCase)

Still gives me the same error

 

[arnelgp]

hmm, can you check if there are controls (tbox, combo) that have
Expression as their ControlSource, like:

=someExpression

or there are controls that are Locked.

 

[vanzie]

There is one control yes that has the expression to display the age from the DOB value but the age value does not save to the table

 

[Gasman]

And if you walk through your code, you will likely find it balks on that control.
If a control has an expression, you cannot assign anything to it.

 

[CJ_London]

have you stepped through the code to see if it is happening with every control or just one

edit: beaten too it

just put debug.print ctrl.name before your strconv line

 

[vanzie]

And if you walk through your code, you will likely find it balks on that control.
If a control has an expression, you cannot assign anything to it.

But now I don't understand is that I've gone through another database I designed and the exact method I used there, is used in this one. Same age display textbox with the expression and it saves perfectly without error.

 

[vanzie]

have you stepped through the code to see if it is happening with every control or just one

edit: beaten too it

When it shows me the error and I click debug, it highlights this part:

ctrl = StrConv(ctrl, vbUpperCase)

same with @arnelgp code:

ctrl = StrConv(ctrl & "", vbUpperCase)

 

[CJ_London]

think we understand that - we are asking what is the name of the control? and what is the value of that control?

 

[arnelgp]

so exclude the Age textbox:

Dim ctrl As Control
For Each ctrl In Detail.Controls
    If (TypeOf ctrl Is TextBox Or TypeOf ctrl Is ComboBox) Then
        If Left$(ctrl.ControlSource & "", 1) = "=" Or ctrl.Locked Then
        Else
            ctrl = StrConv(ctrl & "", vbUpperCase)
        End If
    End If
Next

 

[vanzie]

so exclude the Age textbox:

Dim ctrl As Control
For Each ctrl In Detail.Controls
    If (TypeOf ctrl Is TextBox Or TypeOf ctrl Is ComboBox) Then
        If Left$(ctrl.ControlSource & "", 1) = "=" Or ctrl.Locked Then
        Else
            ctrl = StrConv(ctrl & "", vbUpperCase)
        End If
    End If
Next

That works perfectly. Thank you

 

[Gasman]

so exclude the Age textbox:

Dim ctrl As Control
For Each ctrl In Detail.Controls
    If (TypeOf ctrl Is TextBox Or TypeOf ctrl Is ComboBox) Then
        If Left$(ctrl.ControlSource & "", 1) = "=" Or ctrl.Locked Then
        Else
            ctrl = StrConv(ctrl & "", vbUpperCase)
        End If
    End If
Next

I thought Locked was just for the user interface?

 

[vanzie]

I thought Locked was just for the user interface?

My thoughts exactly

 

[arnelgp]

I thought Locked was just for the user interface?

if the control is Locked, you can't assign value to it.
error will occur if you try.

 

[Gasman]

if the control is Locked, you can't assign value to it.
error will occur if you try.

Sorry Arnel, I would beg to differ (well in 2007 at least).
I locked a control, and was still able to set a value within code.? I did this after my post to see for myself. Bound or Unbound?
However there was not any expression in the control source.

 

[arnelgp]

Sorry Arnel, I would beg to differ (well in 2007 at least).

i tested it and you are correct.
so it is safe to remove it from the code.