Problem with checkboxes after Service Pack 3

I am current experiencing problems with the checkboxes on my forms. If
unchecked, clicking will set the checkbox. If already checked, clicking will
have no effect. Setting a checkbox that is already checked to false still
shows true (via vba).

The forms are bound to a SQL Server back end database. Almost all of the
checkboxes have no code attached to them. The remaining checkboxes just tab
to another field after update. I have decompiled and recompiled.

Tabbing to the checkbox and hitting the spacebar works but not clicking with
the mouse. The problems began after Office Service Pack 3 was installed. I
have many versions of the database that were created before the Service Pack
and none of them have working checkboxes now (they worked before the Service
Pack).

An additional problem occurred with a listbox that had 13 columns. The form
would not display, I could not compile. I could not save until I reduced the
number of columns and save the database.

Any help on the checkboxes would be greatly appreciated.

~Gardner

I fogot to mention, that I am running Access 2003 The application does not
work as and ADP or an ADE file. I execute routines in the MouseHook.dll at
startup. Removing the routines seems to have no effect.

Thanks.

~Gardner

"Gardner" wrote:

I am current experiencing problems with the checkboxes on my forms. If
unchecked, clicking will set the checkbox. If already checked, clicking will
have no effect. Setting a checkbox that is already checked to false still
shows true (via vba).

The forms are bound to a SQL Server back end database. Almost all of the
checkboxes have no code attached to them. The remaining checkboxes just tab
to another field after update. I have decompiled and recompiled.

Tabbing to the checkbox and hitting the spacebar works but not clicking with
the mouse. The problems began after Office Service Pack 3 was installed. I
have many versions of the database that were created before the Service Pack
and none of them have working checkboxes now (they worked before the Service
Pack).

An additional problem occurred with a listbox that had 13 columns. The form
would not display, I could not compile. I could not save until I reduced the
number of columns and save the database.

Any help on the checkboxes would be greatly appreciated.

~Gardner

It's a bug that has been introduced by 2003 SP3. MS is aware of it.

--

Ken Snell
MS ACCESS MVP

"Gardner" wrote in message
...
I am current experiencing problems with the checkboxes on my forms. If
unchecked, clicking will set the checkbox. If already checked, clicking
will
have no effect. Setting a checkbox that is already checked to false still
shows true (via vba).

The forms are bound to a SQL Server back end database. Almost all of the
checkboxes have no code attached to them. The remaining checkboxes just
tab
to another field after update. I have decompiled and recompiled.

Tabbing to the checkbox and hitting the spacebar works but not clicking
with
the mouse. The problems began after Office Service Pack 3 was installed. I
have many versions of the database that were created before the Service
Pack
and none of them have working checkboxes now (they worked before the
Service
Pack).

An additional problem occurred with a listbox that had 13 columns. The
form
would not display, I could not compile. I could not save until I reduced
the
number of columns and save the database.

Any help on the checkboxes would be greatly appreciated.

~Gardner

Thanks Ken.

Are they also aware of the problem with the listbox as well?

~Gardner


"Ken Snell (MVP)" wrote:

It's a bug that has been introduced by 2003 SP3. MS is aware of it.

--

Ken Snell
MS ACCESS MVP

"Gardner" wrote in message
...
I am current experiencing problems with the checkboxes on my forms. If
unchecked, clicking will set the checkbox. If already checked, clicking
will
have no effect. Setting a checkbox that is already checked to false still
shows true (via vba).

The forms are bound to a SQL Server back end database. Almost all of the
checkboxes have no code attached to them. The remaining checkboxes just
tab
to another field after update. I have decompiled and recompiled.

Tabbing to the checkbox and hitting the spacebar works but not clicking
with
the mouse. The problems began after Office Service Pack 3 was installed. I
have many versions of the database that were created before the Service
Pack
and none of them have working checkboxes now (they worked before the
Service
Pack).

An additional problem occurred with a listbox that had 13 columns. The
form
would not display, I could not compile. I could not save until I reduced
the
number of columns and save the database.

Any help on the checkboxes would be greatly appreciated.

~Gardner

Yes.
--

Ken Snell
MS ACCESS MVP


"Gardner" wrote in message
...
Thanks Ken.

Are they also aware of the problem with the listbox as well?

~Gardner

On Sep 28, 9:10 pm, "Ken Snell \(MVP\)"
wrote:
It's a bug that has been introduced by 2003 SP3. MS is aware of it.

--

Ken Snell
MS ACCESS MVP

"Gardner" wrote in message

...

I am current experiencing problems with the checkboxes on my forms. If
unchecked, clicking will set the checkbox. If already checked, clicking
will
have no effect. Setting a checkbox that is already checked to false still
shows true (via vba).

The forms are bound to a SQL Server back end database. Almost all of the
checkboxes have no code attached to them. The remaining checkboxes just
tab
to another field after update. I have decompiled and recompiled.

Tabbing to the checkbox and hitting the spacebar works but not clicking
with
the mouse. The problems began after Office Service Pack 3 was installed. I
have many versions of the database that were created before the Service
Pack
and none of them have working checkboxes now (they worked before the
Service
Pack).

An additional problem occurred with a listbox that had 13 columns. The
form
would not display, I could not compile. I could not save until I reduced
the
number of columns and save the database.

Any help on the checkboxes would be greatly appreciated.

~Gardner

Ken,

Can you provide a link to a knowledge base article or a bug database
where this bug is documented by Microsoft? Does Microsoft have a plan
to release a patch to fix this, or is there a workaround available
(other than using the space bar)?

Thanks,
Bradley

No link to a KB article has been released yet. I'm told that MS is very
close to publishing a KB article and "fix" for this issue.
--

Ken Snell
MS ACCESS MVP



"Bradley" wrote in message
ups.com...
On Sep 28, 9:10 pm, "Ken Snell \(MVP\)"
wrote:
It's a bug that has been introduced by 2003 SP3. MS is aware of it.

Ken,

Can you provide a link to a knowledge base article or a bug database
where this bug is documented by Microsoft? Does Microsoft have a plan
to release a patch to fix this, or is there a workaround available
(other than using the space bar)?

Thanks,
Bradley

Ken, is this the same problem that I see now only 0 and -1 in my
listbox/comboboxes?
The ony strange thing is that I saw this before in SP2, I did something in
the table design and the problem was solved, but now I really don't know
anymore what I did, because nothing helps.

When this is the same bug then I'm 'happy'

Thanks in advance.
Arjan

"Ken Snell (MVP)" wrote in message
...
No link to a KB article has been released yet. I'm told that MS is very
close to publishing a KB article and "fix" for this issue.
--

Ken Snell
MS ACCESS MVP



"Bradley" wrote in message
ups.com...
On Sep 28, 9:10 pm, "Ken Snell \(MVP\)"
wrote:
It's a bug that has been introduced by 2003 SP3. MS is aware of it.

Ken,

Can you provide a link to a knowledge base article or a bug database
where this bug is documented by Microsoft? Does Microsoft have a plan
to release a patch to fix this, or is there a workaround available
(other than using the space bar)?

Thanks,
Bradley

The bug noted by the other poster is related to using SQL Server as the
backend for the database. I'm not aware that this bug is manifested in the
displays in comboboxes or listboxes. 0 is the actual value of False (or No
or Off) in ACCESS; -1 is the actual value of True (or Yes or On).

You can change the Format property of the combobox to Yes/No, True/False, or
On/Off so that it will show the name instead of the value. This may trigger
a separate bug, related to the use of a Format property for a field that is
in a RowSource query of a combobox or listbox, that SP3 introduced, though.
This separate bug causes a blank display for the combobox or listbox. MS
also is working on that bug.

--

Ken Snell
MS ACCESS MVP




"A. van Huizen" wrote in message
news:HxrNi.4161$Hv4.1208@amstwist00...
Ken, is this the same problem that I see now only 0 and -1 in my
listbox/comboboxes?
The ony strange thing is that I saw this before in SP2, I did something in
the table design and the problem was solved, but now I really don't know
anymore what I did, because nothing helps.

When this is the same bug then I'm 'happy'

Thanks in advance.
Arjan

"Ken Snell (MVP)" wrote in message
...
No link to a KB article has been released yet. I'm told that MS is very
close to publishing a KB article and "fix" for this issue.
--

Ken Snell
MS ACCESS MVP



"Bradley" wrote in message
ups.com...
On Sep 28, 9:10 pm, "Ken Snell \(MVP\)"
wrote:
It's a bug that has been introduced by 2003 SP3. MS is aware of it.

Ken,

Can you provide a link to a knowledge base article or a bug database
where this bug is documented by Microsoft? Does Microsoft have a plan
to release a patch to fix this, or is there a workaround available
(other than using the space bar)?

Thanks,
Bradley

Thanks for your fast reply.

Normally I saw in the listbox 'Yes' and 'No', now I see -1 and 0. I didn't
change something and this db works already since 1 year for a client. And I
see it in every front-end on existing databases since this week. So I think
that it is related to SP3 too.

The format of the Yes/No field in the table is set to Yes/No or True/False.
When I change this, it still doesn't matter.
Also when I make the prefered format in the table design empty.

When I make a simple new database with one table, one field and I display
this in a listbox on a form I see only 0 and -1.

It looks like a bug, because I'm not aware that I can change this format
somewhere besides in the table design.

I hope that you can reproduce the same as I see.
Thanks in advance.
Arjan.


"Ken Snell (MVP)" wrote in message
...
The bug noted by the other poster is related to using SQL Server as the
backend for the database. I'm not aware that this bug is manifested in the
displays in comboboxes or listboxes. 0 is the actual value of False (or No
or Off) in ACCESS; -1 is the actual value of True (or Yes or On).

You can change the Format property of the combobox to Yes/No, True/False,
or On/Off so that it will show the name instead of the value. This may
trigger a separate bug, related to the use of a Format property for a
field that is in a RowSource query of a combobox or listbox, that SP3
introduced, though. This separate bug causes a blank display for the
combobox or listbox. MS also is working on that bug.

--

Ken Snell
MS ACCESS MVP




"A. van Huizen" wrote in message
news:HxrNi.4161$Hv4.1208@amstwist00...
Ken, is this the same problem that I see now only 0 and -1 in my
listbox/comboboxes?
The ony strange thing is that I saw this before in SP2, I did something
in the table design and the problem was solved, but now I really don't
know anymore what I did, because nothing helps.

When this is the same bug then I'm 'happy'

Thanks in advance.
Arjan

"Ken Snell (MVP)" wrote in message
...
No link to a KB article has been released yet. I'm told that MS is very
close to publishing a KB article and "fix" for this issue.
--

Ken Snell
MS ACCESS MVP



"Bradley" wrote in message
ups.com...
On Sep 28, 9:10 pm, "Ken Snell \(MVP\)"
wrote:
It's a bug that has been introduced by 2003 SP3. MS is aware of it.

Ken,

Can you provide a link to a knowledge base article or a bug database
where this bug is documented by Microsoft? Does Microsoft have a plan
to release a patch to fix this, or is there a workaround available
(other than using the space bar)?

Thanks,
Bradley