yes/no field display

[Mary Fran]

When I look at a form on my computer, a yes/no field properly displays as a
check box. When another user looks at the same form (linked to same backend)
hers shows a 0 or -1. How do I fix that?

Thanks!

 

[Dirk Goldgar]

When I look at a form on my computer, a yes/no field properly displays as
a
check box. When another user looks at the same form (linked to same
backend)
hers shows a 0 or -1. How do I fix that?

It seems unlikely that she can be looking at the same *form*. On a form,
you either have a check box control bound to the field, or you have a text
box bound to the field. A check box is not capable of displaying a -1 or 0;
only a check mark or a blank.

It's possible for a developer to code it in such a way that the form either
shows a check box or a text box depending on some criteria, but that's an
unlikely scenario. Are you sure you are talking about a *form*, and not
just about a table opened as a datasheet? Or maybe a form or subform opened
in datasheet view?

 

[Mary Fran]

That is what I would have assumed, also. But I sent her the same frontend
I'm looking at and we are both linked to the same backend. That's what is
confounding me...

 

[Dirk Goldgar]

That is what I would have assumed, also. But I sent her the same frontend
I'm looking at and we are both linked to the same backend. That's what
is
confounding me...

Is this form in datasheet view?

 

[Mary Fran]

No, it's a single record form with a subform. This particular field is an
unbound listbox whose row source is a query providing the yes/no field data.

 

[Dirk Goldgar]

No, it's a single record form with a subform. This particular field is
an
unbound listbox whose row source is a query providing the yes/no field
data.

So you're seeing a check box in the item list of a list box, and she isn't?
Now I'm really confused, because I don't think it's possible for a native
Access list box control to show a check box in its list. The columns of a
list box are all strings. I must be completely misunderstanding what's
going on. What version of Access are we talking about?

If you're interested in sending me a (hopefully reduced) copy of your
front-end, in hopes of my coming to an understanding of what's going on, I'd
be willing to look at it, time permitting. You can send to the address you
get by removing NO SPAM and ".invalid" from the reply-address of this
message, or you can get my address from the website in my sig.

 

[Mary Fran]

Before you go to that trouble, I apologize for my confusing explanation. I
am not seeing a checkbox unless I open the row source query - I am seeing a
"Yes" or "No" in the listbox and the other user is seeing a 0 or -1. If you
would still like a copy of the form I'd be happy to provide it.

Thank you.

 

[Dirk Goldgar]

Before you go to that trouble, I apologize for my confusing explanation.
I
am not seeing a checkbox unless I open the row source query - I am seeing
a
"Yes" or "No" in the listbox and the other user is seeing a 0 or -1. If
you
would still like a copy of the form I'd be happy to provide it.

Okay, that makes a lot more sense, though I'm not completelty sure what's
causing the difference. No, I don't think I need to see the form.

You say you are using the same front-end. But is every aspect of the table
design identical in the back-end? In particular, is the Format property of
the field, in the design view of the table, the same in your copy of the
back-end as in hers? I believe that, when the field is converted to text
for display in the list box, the format used will be the format that is
inherited from the Format property of the field in the table, unless that is
modified by the Format property of the field in the query's design view
(which would only apply if your rowsource is a stored query). If, for
example, in your table design view, the field has "Yes/No" for its Format
property, while in your other user's table the field has a blank Format
property, then I'm pretty sure you'd get the different results you report.

 

[Mary Fran]

That's why I had her send me her backend. We are linked to identical
backends now also. And I double-checked the table design format property -
it is yes/no and there's no overriding format in the query, which is not a
stored query. So are you saying that if we both are truly looking at exactly
the same front and back ends there is no way she could be getting the 0's and
-1's while I get yes/no's?

 

[Dirk Goldgar]

That's why I had her send me her backend. We are linked to identical
backends now also. And I double-checked the table design format
property -
it is yes/no and there's no overriding format in the query, which is not a
stored query. So are you saying that if we both are truly looking at
exactly
the same front and back ends there is no way she could be getting the 0's
and
-1's while I get yes/no's?

I wouldn't go that far. I'm saying that I don't know why she would be. If
the front-ends and back-ends are truly identical, and you're using the same
version of Access (not that I see why that would make a difference), I'm
currently at a loss. I can easily think of a way to work around it -- use a
rowsource query that explicitly formats the field to "Yes/No" format -- but
I have no idea why it's happening. The only thing I can conceive of is some
setting for the Access application itself, but I don't know what that would
be.

 

[Linq Adams via AccessMonster.com]

You aren't using ACC2003 by any chance, are you? If so, check to see if one
of the machines (hers or yours) has SP3 installed and the other doesn't. SP3,
if I remember correctly, is doing some strange things to Yes/No fields.

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via AccessMonster.com

 

[Mary Fran]

I am using ACC2003 but SP2 so I will see what her version is on Monday
morning - in the meantime, I'll go ahead with Dirk's advice to format the
rowsource query field - thanks for all your attention to this frustrating
matter!!!!!!!!!!

 

[Linq Adams via AccessMonster.com]

I wouldn't do that yet, either! If the problem is that the other machine has
SP3 installed, formatting the field to be displayed in a listbox may make the
field disappear completely; another SP3 bug!

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via AccessMonster.com

 

[Dirk Goldgar]

I wouldn't do that yet, either! If the problem is that the other machine
has
SP3 installed, formatting the field to be displayed in a listbox may make
the
field disappear completely; another SP3 bug!

I don't think that will happen if she uses the Format function to create a
calculated field in the query, as I suggested. I could be wrong, but I
think the bug you're talking about occurs when there's a format property
applied to the field in the table.