Problem #3 Yes/No fields in Combo and List Boxes

  • Thread starter Thread starter Cheval
  • Start date Start date
C

Cheval

I know the work around is to use the IIF([Field],"Yes","No") statement, but
is this going to be fixed or is there a need to have it this way from now on?
 
I'm not sure anything needs fixing. Could you be more specific about your
expectations?
 
Hi Duane,

My expectation is restoring the usage functionality of the Yes/No fields in
Combo boxes and List Boxs to the pre-Office 2003 SP3 functionality. It's been
this way since Office 95 and there is a lot of code using it with this
pattern.

Duane Hookom said:
I'm not sure anything needs fixing. Could you be more specific about your
expectations?

--
Duane Hookom
Microsoft Access MVP


Cheval said:
I know the work around is to use the IIF([Field],"Yes","No") statement, but
is this going to be fixed or is there a need to have it this way from now on?
Click to expand...
Click to expand...
 
I'm still not sure what "functionality" you are referring to. You haven't
stated what, only that it is gone.

--
Duane Hookom
Microsoft Access MVP


Cheval said:
Hi Duane,

My expectation is restoring the usage functionality of the Yes/No fields in
Combo boxes and List Boxs to the pre-Office 2003 SP3 functionality. It's been
this way since Office 95 and there is a lot of code using it with this
pattern.

Duane Hookom said:
I'm not sure anything needs fixing. Could you be more specific about your
expectations?

--
Duane Hookom
Microsoft Access MVP


Cheval said:
I know the work around is to use the IIF([Field],"Yes","No") statement, but
is this going to be fixed or is there a need to have it this way from now on?
Click to expand...
Click to expand...
Click to expand...
 
Hi Duane,

ok Sorry yes. If the field data type is set to Yes/No then display this in
the Combo/List box field. Or if it set to True/False, then likewise display
this. Simple as that.

Duane Hookom said:
I'm still not sure what "functionality" you are referring to. You haven't
stated what, only that it is gone.

--
Duane Hookom
Microsoft Access MVP


Cheval said:
Hi Duane,

My expectation is restoring the usage functionality of the Yes/No fields in
Combo boxes and List Boxs to the pre-Office 2003 SP3 functionality. It's been
this way since Office 95 and there is a lot of code using it with this
pattern.

Duane Hookom said:
I'm not sure anything needs fixing. Could you be more specific about your
expectations?

--
Duane Hookom
Microsoft Access MVP


:

I know the work around is to use the IIF([Field],"Yes","No") statement, but
is this going to be fixed or is there a need to have it this way from now on?
Click to expand...
Click to expand...
Click to expand...
 
The datatype is yes/no which stores either -1 or 0. I assume you expect the
"format" property set in the field properties to carry through to the combo
box display. I don't generally set the format properties in the table design
so I have always set the row source query to display exactly what I want.

I'm not sure what your combo boxes are displaying (maybe -1 or 0). It's easy
enough to change this but I can see where it might be annoying if the
behaviour has changed.
--
Duane Hookom
Microsoft Access MVP


Cheval said:
Hi Duane,

ok Sorry yes. If the field data type is set to Yes/No then display this in
the Combo/List box field. Or if it set to True/False, then likewise display
this. Simple as that.

Duane Hookom said:
I'm still not sure what "functionality" you are referring to. You haven't
stated what, only that it is gone.

--
Duane Hookom
Microsoft Access MVP


Cheval said:
Hi Duane,

My expectation is restoring the usage functionality of the Yes/No fields in
Combo boxes and List Boxs to the pre-Office 2003 SP3 functionality. It's been
this way since Office 95 and there is a lot of code using it with this
pattern.

:

I'm not sure anything needs fixing. Could you be more specific about your
expectations?

--
Duane Hookom
Microsoft Access MVP


:

I know the work around is to use the IIF([Field],"Yes","No") statement, but
is this going to be fixed or is there a need to have it this way from now on?
Click to expand...
Click to expand...
Click to expand...
 
Hi Duane,

Yes that is the whole point. There is a lot of code that took advantage of
the initial format behavior but in Service Pack 3 that behavior is now
broken. Which means a lot updating queries and the like with
IIF([Field],"Yes","No") IIF([Field],"True","False") statements.

I can't see any security benefit, therefore to me it is an introduced
oversight bug.

Duane Hookom said:
The datatype is yes/no which stores either -1 or 0. I assume you expect the
"format" property set in the field properties to carry through to the combo
box display. I don't generally set the format properties in the table design
so I have always set the row source query to display exactly what I want.

I'm not sure what your combo boxes are displaying (maybe -1 or 0). It's easy
enough to change this but I can see where it might be annoying if the
behaviour has changed.
--
Duane Hookom
Microsoft Access MVP


Cheval said:
Hi Duane,

ok Sorry yes. If the field data type is set to Yes/No then display this in
the Combo/List box field. Or if it set to True/False, then likewise display
this. Simple as that.

Duane Hookom said:
I'm still not sure what "functionality" you are referring to. You haven't
stated what, only that it is gone.

--
Duane Hookom
Microsoft Access MVP


:

Hi Duane,

My expectation is restoring the usage functionality of the Yes/No fields in
Combo boxes and List Boxs to the pre-Office 2003 SP3 functionality. It's been
this way since Office 95 and there is a lot of code using it with this
pattern.

:

I'm not sure anything needs fixing. Could you be more specific about your
expectations?

--
Duane Hookom
Microsoft Access MVP


:

I know the work around is to use the IIF([Field],"Yes","No") statement, but
is this going to be fixed or is there a need to have it this way from now on?
Click to expand...
Click to expand...
Click to expand...
 
Further to this, there is now a hotfix available kb945674.

Cheval said:
Hi Duane,

Yes that is the whole point. There is a lot of code that took advantage of
the initial format behavior but in Service Pack 3 that behavior is now
broken. Which means a lot updating queries and the like with
IIF([Field],"Yes","No") IIF([Field],"True","False") statements.

I can't see any security benefit, therefore to me it is an introduced
oversight bug.

Duane Hookom said:
The datatype is yes/no which stores either -1 or 0. I assume you expect the
"format" property set in the field properties to carry through to the combo
box display. I don't generally set the format properties in the table design
so I have always set the row source query to display exactly what I want.

I'm not sure what your combo boxes are displaying (maybe -1 or 0). It's easy
enough to change this but I can see where it might be annoying if the
behaviour has changed.
--
Duane Hookom
Microsoft Access MVP


Cheval said:
Hi Duane,

ok Sorry yes. If the field data type is set to Yes/No then display this in
the Combo/List box field. Or if it set to True/False, then likewise display
this. Simple as that.

:

I'm still not sure what "functionality" you are referring to. You haven't
stated what, only that it is gone.

--
Duane Hookom
Microsoft Access MVP


:

Hi Duane,

My expectation is restoring the usage functionality of the Yes/No fields in
Combo boxes and List Boxs to the pre-Office 2003 SP3 functionality. It's been
this way since Office 95 and there is a lot of code using it with this
pattern.

:

I'm not sure anything needs fixing. Could you be more specific about your
expectations?

--
Duane Hookom
Microsoft Access MVP


:

I know the work around is to use the IIF([Field],"Yes","No") statement, but
is this going to be fixed or is there a need to have it this way from now on?
Click to expand...
Click to expand...
Click to expand...
 
Back
Top