Access 2003 service pack 2

[UncleOli]

Ever since I installed Microsoft Access 2003 Service Pack 2 on 03.13.06 on
Windows XP Professional, compacting any of my database files after doing any
kind of editing in Visual Basic Editor closes Access with the following
message:

"Microsoft Office Access has encountered a problem and needs to close. We
are sorry for the incovenience."

An article at support.microsoft.com reports that this problem was addressed
by Service Pack 1, but I did not have the problem until after installing
Microsoft Office Service Pack 2.

Is there any way to uninstall Service Pack 2?

 

[Tom Wickerath]

Hi UncleOli,

Lots of people are running SP-2 without a similar problem. The only issue
with SP-2 is the inability to edit data in a linked Excel spreadsheet, but
that is by design.

You may have gotten a bad installation. Have you tried Help > Detect and
Repair?

Don't know if there is a way to uninstall SP-2.


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Arvin Meyer [MVP]]

Depending upon your permission level on your machine, you can uninstall by
going to the Control Panel, choosing Add\Remove Programs and finding SP2 to
uninstall. Be aware that much of SP2 deals with security issues that will
leave you exposed when you've uninstalled it. A much better solution would
be to reinstall Office or do a Repair of the Office installation.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[david epsom dot com dot au]

Compacting a database from the Access menu or Access
command line also 'compacts' the VBA project, within
it's record.

The VBA project is apparently stored as a single binary
object. Making changes to forms and reports and code
modules can change the length of the form/report/code
module, leading to fragmentation inside the binary object.

You apparently have a slightly corrupt VBA project,
at least by the standards of 2003 SP2, and Access
is bailing out when attempting the compact.

The obvious step would be to /decompile, but that
hardly ever gives you a final resolution at this stage.
I would go straight to the export/import code,

http://groups.google.com.au/group/c..._frm/thread/a3fd9ad10f17709d/502fb22f214f62f5

and create a new database.

Sometimes even this doesn't really work: it seems that
some forms are just too complex in the wrong way for
Access, and it always gets confused.

(david)

 

[UncleOli]

Tom,

Thank you for your suggestion. I was not aware of Help > Detect and Repair,
but I ran it to no benefit. I'm doing further troubleshooting to pinpoint the
problem and will post my findings here to follow up.

Thanks again,
Oli
(e-mail address removed)
03.21.06 17.23 hst

 

[UncleOli]

Arvin,

Microsoft Office 2003 Service Pack 2 was not listed in my Add/Remove
Programs list, but I had already run Repair of the Office Installation. It
did not seem to help any. I'm doing further troubleshooting to pinpoint the
problem and will post my findings here to follow up.

Thank you,
Oli
(e-mail address removed)
03.21.06 17.29 hst

 

[UncleOli]

David,

Thank you for your post. The problem seems to affect all of my Access
database files, so I am trying to pinpoint what they might have in common in
terms of corrupted code.

I have already also tested the program installation itself, by running one
of the database files on another PC, where it ran without problems. However,
I noticed that the second PC had not had Microsoft Office 2003 Service Pack 2
installed. When I updated it with Service Pack 2, the same problem resulted!

I'm doing further troubleshooting to pinpoint the problem and will post my
findings here to follow up. For now, it seems to involve my use of an .mda
file as a reference to share common code (Tools > References).

Thanks again,
Oli
(e-mail address removed)
03.21.06 17.49 hst

 

[UncleOli]

I have been able to recreate the error with the following procedure. To
minimize the possibility of corrupted code, the programming in VBA for this
test is kept to a minimum. I would appreciate knowing what results from
anyone else duplicating these steps. Is this a bug with Access 2003 Service
Pack 2 or am I missing something?

Create a library database and save it as an add-in (.mda): call it
"library.mda".
Create a VBA module without adding any code to it: "Module1".
Create a new database (.mdb): "db1.mdb".
Create a VBA module without adding any code to it: "Module1".
In VBA edit mode, add the library database as a reference (Tools >
References).
Close VBA.
What we now have is a database file db1.mdb that is basically empty except
for a reference to what is essentially an empty library,minimizing the
possibility of any corrupted code involved.
Compact the database file while it is still open.
At this point in my test, Access aborts and returns the error message
referenced earlier.

Thank you,
Oli Bautista
03.22.06 07.41 hst

 

[Mohamed]

I have similar problem after installing IE7 and Microsoft Access 2003 Service
Pack 2 on Windows XP Professional, compacting any of my database files keep
closing MS Access with the following message:

"Microsoft Office Access has encountered a problem and needs to close. We
are sorry for the incovenience."

Anyone has same problem VBA Mcro MS Access 2003 sp2 and IE7 ?

Thank you and any help is appreciated.

Mohamed Elhalwagy

 

[Clif McIrvin]

I've been running Access (Office) 2003 SP3 with hotfix on XP SP2 without
any trouble such as you describe. Any reason you're not upgrading to
2003 SP3? SP3 did include security patches....

--
Office / Access 2003 SP3 requires a necessary hotfix:

http://support.microsoft.com/kb/945674

 

[Mohamed]

I updated MS Office SP3 and I still having problem with IE7 and MS Acces 2003
SP3 VBA Macro.

Any help on this is appreciated.


Thanks


Mohamed Elhalwagy

 

[Clif McIrvin]

Did you also install that hotfix? That is an extra step after you have
SP3 installed (the link is below)

 

[Mohamed]

Clif,

Yes, I did install the hotfix as well after the SP3 of Office 2003 and MS
Access Macro still aborting and give me tha same message. The Macro was
written on MS Access 2003 sp2 ans was running until I installed IE7. Other
people running IE6 are fine with SP2 and SP3.

" Microsoft Office Access has encountered a problem and needs to close. We
are sorry for the inconvenience. "

Thanks


Mohamed Elhalwagy

 

[Clif McIrvin]

Clif,

Yes, I did install the hotfix as well after the SP3 of Office 2003 and
MS
Access Macro still aborting and give me tha same message. The Macro
was
written on MS Access 2003 sp2 ans was running until I installed IE7.
Other
people running IE6 are fine with SP2 and SP3.

" Microsoft Office Access has encountered a problem and needs to
close. We
are sorry for the inconvenience. "

Thanks


Mohamed Elhalwagy

Sorry - that exhausts my ideas. Anyone else have any suggestions for
Mohamed?

 

[Tom Wickerath]

Hi Mohamed,

Does this happen with any database you use on this machine, or with just one
particular database? If the answer is the former, then you most likely have a
damaged installation of Access and you may have to resort to "flattening" and
re-loading everything. If the answer is the latter, then you may be able to
recover the database using the steps that I outline on the bottom of page 3
of a Word document that I call Access Links.doc. You are welcome to download
a zipped copy from this site:

http://www.accessmvp.com/TWickerath/


Good Luck,


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________