Microsoft Office Service Pack 3 Problem

[Guest]

Hi All.

Since installing Office 2003 Service Pack 3 we have been experiencing
problems on multiple machines with data entry in an Access 2003 form linked
directly to the table in a Project file.

The table has 3 bit fields whose default value is Zero in each case. The
form has a CheckBox for each of these fields. Again the default property
inherits the 0 default value from the table. The form also has a before
insert event that retrieves some values via an ADO recordset to populate some
other fields. As soon as the first value has been retrieved the form sets the
value in each of the bit fields to 1 even though the user did not enter
anything into these fields. At this point the user tries to amend the
incorrect values but can't it appears that the 3 CheckBox controls are locked
even thought the Locked property is set to False.

Once the record has been saved then the user can remove the offending values
in the bit fields.

There is no code in the entire project file that sets the value of these bit
fields so why is it setting the values to the opposite of the defualt value?

This form and code have worked perfectly for months. Now service pack 3 has
come along and Wham.

I have now uninstalled Office and re-installed and patched up to service
pack 2 and all is well.

I tried to contact Microsoft Technical Support but they wanted my firm to
pay them £199 + VAT for the support call to tell them they have got a problem
with their software!! I don't think so. That's worse than Highway Robbery.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...-a083-fdc808a2f019&dg=microsoft.public.access

 

[Jeff Boyce]

It may be that others have posted the same issue that you found. Try using
an on-line search engine to look.

What I have seen is that tables that have formatting applied to fields cause
forms based on those tables to break.

Any chance your underlying tables have formatting?

--
Regards

Jeff Boyce
www.InformationFutures.net

Microsoft Office/Access MVP


Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

Hi All.

Since installing Office 2003 Service Pack 3 we have been experiencing
problems on multiple machines with data entry in an Access 2003 form linked
directly to the table in a Project file.

The table has 3 bit fields whose default value is Zero in each case. The
form has a CheckBox for each of these fields. Again the default property
inherits the 0 default value from the table. The form also has a before
insert event that retrieves some values via an ADO recordset to populate some
other fields. As soon as the first value has been retrieved the form sets the
value in each of the bit fields to 1 even though the user did not enter
anything into these fields. At this point the user tries to amend the
incorrect values but can't it appears that the 3 CheckBox controls are locked
even thought the Locked property is set to False.

Once the record has been saved then the user can remove the offending values
in the bit fields.

There is no code in the entire project file that sets the value of these bit
fields so why is it setting the values to the opposite of the defualt value?

This form and code have worked perfectly for months. Now service pack 3 has
come along and Wham.

I have now uninstalled Office and re-installed and patched up to service
pack 2 and all is well.

I tried to contact Microsoft Technical Support but they wanted my firm to
pay them £199 + VAT for the support call to tell them they have got a problem
with their software!! I don't think so. That's worse than Highway Robbery.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...-a083-fdc808a2f019&dg=microsoft.public.access

 

[niobium]

I have been searching for something about this for hours. The exact
same thing has happened to me--everything seemed fine, now after an
update to SP3 for Office 2003, every bit field in my SQL Server
Express backend that was hooked up to a checkbox on the Access 2003
Data Project front-end is getting temporarily assigned "true" on the
Data Project side when an insertion runs. Furthermore I can't even get
checkboxes to "uncheck" i.e. make a true->false transition. They can
set a field to true from false, but not vice versa.

I confirmed this is not just related to a Form with a view for a data
source; I made a plain, empty form, bound it to one of my bit-field
containing tables (not to a View or an SP), bound a checkbox to one of
those fields, and I can check the box, but not uncheck it.

I did a bit of testing using Management Studio and it's definitely not
a SQL Server Express error in terms of record insertion (not sure
about translation of the form data from False/True to 0/1). Insertions
there behave as expected; bit fields defaulted to 0 behave
accordingly. I initially suspected that SSE's defaults were somehow
involved but since those default to False, not true--and for both
Access and SSE False is 0--that doesn't explain it.

Has anyone found a solution to this yet?

--Nb41

 

[niobium]

Dug around on other forums and found the official bug report:
http://support.microsoft.com/kb/943967

So, for anyone else hitting this, don't upgrade your users to SP3. If
you did, you have to roll back, or switch to an Option Frame. It's an
acknowledged problem, but, no word on when we can expect a fix.

--Nb41

 

[Linq Adams via AccessMonster.com]

Allen Browne posts probably the most up to date list of the SP3 bugs on his
site if anyone wants to know what's lurking! He also suggests some
workarounds. If you want to dump SP3, you have to uninstall Access then re-
install theu SP2.

http://allenbrowne.com/tips.html

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

Answers/posts based on Access 2000/2003

Message posted via AccessMonster.com