By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,824 Members | 2,410 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,824 IT Pros & Developers. It's quick & easy.

Problem with MS-Access 2003 Listbox display

P: n/a
At one of my client sites we noticed a few weeks ago that Listboxes
which previously showed "Yes" or "No" are now showing "-1" or "0". The
underlying tables and queries are displaying True/False fields
correctly and I suspect this problem is related to Service Pack 3.

I haven't been able to find any other posts on the Net about this
problem?

Has anyone else noticed this and more importantly, is there a solution?

Oct 10 '07 #1
Share this Question
Share on Google+
4 Replies


P: n/a
ch******@gmail.com wrote:
At one of my client sites we noticed a few weeks ago that Listboxes
which previously showed "Yes" or "No" are now showing "-1" or "0". The
underlying tables and queries are displaying True/False fields
correctly and I suspect this problem is related to Service Pack 3.

I haven't been able to find any other posts on the Net about this
problem?

Has anyone else noticed this and more importantly, is there a solution?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I don't know what you mean by "The underlying tables and queries are
displaying True/False fields correctly...." (What's correct?) So, I
suggest you could change the ListBox's RowSource property to a SELECT
statement that includes an expression like this:

IIf(yes_no_column=-1, "Yes","No") As YesNo

for the table's Yes/No column (change the column name to your column
name).

If you allow NULLs in the Yes/No column (ugh) the expression would be
like this:

IIF(yes_no_column IS NULL,"UNK",IIf(yes_no_column=-1,"Yes","No"))
UNK stands for "unknown."

Relying on any control to "correctly" display the same format as the
source table is "iffy" at best. Who knows what may happen in the
future? It's always best to explicitly declare how you want the data to
be displayed.
--
MGFoster:::mgf00 <atearthlink <decimal-pointnet
Oakland, CA (USA)
** Respond only to this newsgroup. I DO NOT respond to emails **

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBRwwtn4echKqOuFEgEQKSvQCdGcdd23rBWNTY4wNG3WYXeH 27K9wAoMzV
iX9aLbfsmMGN1J6h00t6pnan
=NFf6
-----END PGP SIGNATURE-----
Oct 10 '07 #2

P: n/a
On Oct 10, 11:40 am, MGFoster <m...@privacy.comwrote:
chelt...@gmail.com wrote:
At one of my client sites we noticed a few weeks ago that Listboxes
which previously showed "Yes" or "No" are now showing "-1" or "0". The
underlying tables and queries are displaying True/False fields
correctly and I suspect this problem is related to Service Pack 3.
I haven't been able to find any other posts on the Net about this
problem?
Has anyone else noticed this and more importantly, is there a solution?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I don't know what you mean by "The underlying tables and queries are
displaying True/False fields correctly...." (What's correct?) So, I
suggest you could change the ListBox's RowSource property to a SELECT
statement that includes an expression like this:

IIf(yes_no_column=-1, "Yes","No") As YesNo

for the table's Yes/No column (change the column name to your column
name).

If you allow NULLs in the Yes/No column (ugh) the expression would be
like this:

IIF(yes_no_column IS NULL,"UNK",IIf(yes_no_column=-1,"Yes","No"))

UNK stands for "unknown."

Relying on any control to "correctly" display the same format as the
source table is "iffy" at best. Who knows what may happen in the
future? It's always best to explicitly declare how you want the data to
be displayed.
--
MGFoster:::mgf00 <atearthlink <decimal-pointnet
Oakland, CA (USA)
** Respond only to this newsgroup. I DO NOT respond to emails **

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBRwwtn4echKqOuFEgEQKSvQCdGcdd23rBWNTY4wNG3WYXeH 27K9wAoMzV
iX9aLbfsmMGN1J6h00t6pnan
=NFf6
-----END PGP SIGNATURE-----
Agree, but all was well until about 3 weeks ago.

Yes, I can change the Rowsource for all affected Listboxes but I am
curious to know why this has suddenly changed? Service Pack 3 appears
to be the culprit!

Surely someone else has seen this problem?

PeCo

Oct 10 '07 #3

P: n/a
ch******@gmail.com wrote:
On Oct 10, 11:40 am, MGFoster <m...@privacy.comwrote:
>>chelt...@gmail.com wrote:
>>>At one of my client sites we noticed a few weeks ago that Listboxes
which previously showed "Yes" or "No" are now showing "-1" or "0". The
underlying tables and queries are displaying True/False fields
correctly and I suspect this problem is related to Service Pack 3.
>>>I haven't been able to find any other posts on the Net about this
problem?
>>>Has anyone else noticed this and more importantly, is there a solution?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I don't know what you mean by "The underlying tables and queries are
displaying True/False fields correctly...." (What's correct?) So, I
suggest you could change the ListBox's RowSource property to a SELECT
statement that includes an expression like this:

IIf(yes_no_column=-1, "Yes","No") As YesNo

for the table's Yes/No column (change the column name to your column
name).

If you allow NULLs in the Yes/No column (ugh) the expression would be
like this:

IIF(yes_no_column IS NULL,"UNK",IIf(yes_no_column=-1,"Yes","No"))

UNK stands for "unknown."

Relying on any control to "correctly" display the same format as the
source table is "iffy" at best. Who knows what may happen in the
future? It's always best to explicitly declare how you want the data to
be displayed.
--
MGFoster:::mgf00 <atearthlink <decimal-pointnet
Oakland, CA (USA)
** Respond only to this newsgroup. I DO NOT respond to emails **

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBRwwtn4echKqOuFEgEQKSvQCdGcdd23rBWNTY4wNG3WYXeH 27K9wAoMzV
iX9aLbfsmMGN1J6h00t6pnan
=NFf6
-----END PGP SIGNATURE-----


Agree, but all was well until about 3 weeks ago.

Yes, I can change the Rowsource for all affected Listboxes but I am
curious to know why this has suddenly changed? Service Pack 3 appears
to be the culprit!

Surely someone else has seen this problem?

PeCo
I created a table with a YN field. I set the format to nothing. I
created a form with a listbox. The field was displayed as 0 or -1. I
changed the format to Yes/No and it displayed Yes or No. Maybe
somebody's been changing formats.
Oct 10 '07 #4

P: n/a
Sky
It's likely this SP3 formatting bug for combo boxes and list boxes:

http://groups.google.com/group/micro...a6789bd55fe15d

No fix from Microsoft that I have seen.

Workaround: remove the underlying field format property in the table, or
reformulate the list box RowSource.

- Steve

<ch******@gmail.comwrote in message
news:11**********************@22g2000hsm.googlegro ups.com...
At one of my client sites we noticed a few weeks ago that Listboxes
which previously showed "Yes" or "No" are now showing "-1" or "0". The
underlying tables and queries are displaying True/False fields
correctly and I suspect this problem is related to Service Pack 3.

I haven't been able to find any other posts on the Net about this
problem?

Has anyone else noticed this and more importantly, is there a solution?

Oct 10 '07 #5

This discussion thread is closed

Replies have been disabled for this discussion.