Yes/No Column in ListBox as changed!

HeyMoe

Registered User.
Local time
Tomorrow, 04:06
Joined
Oct 12, 2007
Messages
18
Overnight, a column in a listbox has changed from showing Yes/No to -1/0!
No one touched any formating and the query that populates the listbox still shows yes/no when opened.
Another strange thing is that when I open a backup version from last month, it too now shows -1/0! :confused:

We are all using WindowsXP/Access2003.
Overnight this is happening to all users...accept one!
He is the only user who has his display theme set to "Windows XP".
Everyone else has the theme set to "Windows Classic".

Any suggestions and help would be appreciated.

Thanks.
 
it has nothing to do with the windows theme.

I would say you should populate the listbox again and see what you get...
 
it has nothing to do with the windows theme.
I would say you should populate the listbox again and see what you get...

Thanks for that...?
I've done EVERYTHING I can think of to fix this.
I've copied the table and the query to a new database and then created a new form that contains nothing but a listbox.
Guess, what? It shows -1/0!
Keep in mind that this is now happening in backup versions that never had this problem!!!!!
 
interesting...did you change anything else connected to the listbox?
 
I did find out something late yesterday.
The user where this problem doesn't appear is using Access 2003 with SP2. The rest of us are using SP3!

The attachment should show you what's going on.
 

Attachments

BOB,

didn't you post a link about SP3 awhile back, and how it screwed up some Access databases? That would explain it...
 
Not only is this affecting listboxes, but also checkboxes!
If the query shows yes/no or even 0/-1, any checkboxes are displaying nothing. ie. That grey coloring you get when there is no control.
 
Sorry that I only noticed this post just now, because I knew the answer as soon as I read the first line of the original post! This is, indeed, one of the many evil manifestations of the v2003/SP3 "service" packs, and fortunately one that the hotfix cured! Which is why I always avoid Microsoft "updates" for at least a year after they're released!

For anyone else who wanders by here and is having problems with v2003, here's a list of the bugs compiled by Allen Browne:

http://allenbrowne.com/bug-Access2003SP3.html
 
Sorry that I only noticed this post just now, because I knew the answer as soon as I read the first line of the original post! This is, indeed, one of the many evil manifestations of the v2003/SP3 "service" packs, and fortunately one that the hotfix cured! Which is why I always avoid Microsoft "updates" for at least a year after they're released!

For anyone else who wanders by here and is having problems with v2003, here's a list of the bugs compiled by Allen Browne:

http://allenbrowne.com/bug-Access2003SP3.html

The response I got here completely slaughters that which I got from the company's IT helpdesk! They haven't got back to me yet!:rolleyes:

Thanks to all!
 
GladWeCouldHelp.png
 

Users who are viewing this thread

Back
Top Bottom