Why is Service Pack 3 causing issues with reports in my database?

[Ron]

After installing Service Pack 3 for Microsoft Office 2003, a database we use
begins crashing for no reason when we attempt to open some reports. After
uninstalling, and reinstalling without Service Pack 3, the database's reports
work as they always have.

I have searched and searched for answers to this issue, and have come up
with nothing. MS wants to get CC info just to ask my question, so I'm not
going that route. This is an issue with Service Pack 3, and should be
resolved. The Service Pack 3 update information didn't even mention any
Access-Specific changes that might cause this..

It's not an isolated incident.. No matter what computer I put this on, it
crashes when certain reports are opened. I even tried recreating the problem
reports, and ended up crashing when I tried to save the new report.. Copying
the report(s) results in a crash half (???) of the time.

There are absolutely no issues without Service Pack 3..

I am truly sorry if I posted this in the wrong discussion group. There were
so many in the list, and this seemed the best choice of the group of 'Access'
related groups I saw, while going through the list.

I sure hope someone in the "know" will see this, and help to resolve this
issue, cause I'm tired of Windows Live OneCare and Automatic Update
constantly telling me my system is not up to date because I don't have the
latest service pack for Office.

 

[Sylvain Lafontaine]

As you have a problem with reports, a good newsgroup to post this would have
been m.p.a.reports or even simply m.p.access. This particular newsgroup is
about ADP and SQL-Server and while ADP also has its own issues with SP3, I'm
not sure from your post that you are using an ADP project and not a MDB
file.

Finally, when you are asking a question, it's usually a good idea to provide
some details. Simply saying that Access is crashing when opening some
reports is not going to help you very much.

 

[Tom van Stiphout]

On Fri, 26 Oct 2007 07:10:02 -0700, Ron

There is a known issue with SP3 and bit columns, reported in this
newsgroup. Otherwise your best bet (if you don't want to pay for
support) may be to continue to monitor the MSFT Knowledgebase and
newsgroups for more clues.
Also, using an elimination technique, you may be able to find out what
feature in your report is making Access crash, and then decide if you
can live without it.

-Tom.

 

[df]

After installing Service Pack 3 for Microsoft Office 2003, a database we
use
begins crashing for no reason when we attempt to open some reports. After
uninstalling, and reinstalling without Service Pack 3, the database's
reports
work as they always have.

I have searched and searched for answers to this issue, and have come up
with nothing. MS wants to get CC info just to ask my question, so I'm not
going that route. This is an issue with Service Pack 3, and should be
resolved. The Service Pack 3 update information didn't even mention any
Access-Specific changes that might cause this..

It's not an isolated incident.. No matter what computer I put this on, it
crashes when certain reports are opened. I even tried recreating the
problem
reports, and ended up crashing when I tried to save the new report..
Copying
the report(s) results in a crash half (???) of the time.

There are absolutely no issues without Service Pack 3..

I am truly sorry if I posted this in the wrong discussion group. There
were
so many in the list, and this seemed the best choice of the group of
'Access'
related groups I saw, while going through the list.

I sure hope someone in the "know" will see this, and help to resolve this
issue, cause I'm tired of Windows Live OneCare and Automatic Update
constantly telling me my system is not up to date because I don't have the
latest service pack for Office.