Access 2003 SP2: Is this a bug?

[UncleOli]

This is a follow-up to a previous post under the subject "Access 2003 service
pack 2."

I am running Microsoft Access 2003 on Windows XP Professional. I installed
Microsoft Office Service Pack 2 on 03.13.06, Since then, I have been unable
to successfully compact any open database file after editing in VBA. I have
tried entering VBA and exiting immediately, with the same result. Access
aborts and pops up this message:

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

I have run Repair of the Office Installation in Windows XP's Add or Remove
Programs, which did not seem to help.

I have 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!

What my database files all share in common is a VBA module I have saved as
an add-in, which I am using as a library database (in VBA, Tools >
Reference). I have run the following test to recreate the problem:

To minimize the possibility of corrupted code, the programming in VBA for
this test is kept to a minimum.

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.

The result 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.

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?

Thank you,
Oli
03.23.06 08.51 hst

 

[Wayne Morgan]

I get the same problem. I have SP2 installed, I haven't tried without SP2. I
will pass this on.

 

[UncleOli]

Thank you for confirming the problem.

For your info, I am able to work around the problem by turning off Compact
on Close for the database file I'm working on. At that point, I am able to
successfully compact from that source file to another destination file. I
have been able to compile a new mde file, but have not done much testing of
the resulting executable file.

Thanks again,
Oli
03.23.06 10.27 hst

 

[david epsom dot com dot au]

FWIW, I see this behaviour only with the A2K3 files.

Not when I open our secured A2K mdb or mde with A2K
mde references,

Win XP. A2K3, 11.6566.6568, SP2.



(david)