MSACCESS.EXE in TaskManager

[lillian]

Hello. I am having a problem with opening one of my database programs.
What I have to do is go to the Task Manager, find the MSACCESS.EXE process
and kill it. I then can open my database file. I have trouble shooted it
to a single report. If I open this report manually and close it, the
MSACCESS.EXE process must be killed every time so this database will open.

The report has no vba code in it just a simple report with a query record
source.


I open the database with exclusive and no record locking

I don't know how to fix this problem.
any ideas would be appreciated.

 

[Allen Browne]

What version of Access is this?

Do you have the latest service pack for your version of Access? See:
http://support.microsoft.com/sp

Does the query call any VBA code?

(I assume the problem occurs if you open the report directly from the
Database window, i.e. not through code.)

Does a compact, decompile, compact, compile sequence help? Details:
http://allenbrowne.com/recover.html

 

[lillian]

What version of Access is this?

Do you have the latest service pack for your version of Access? See:
http://support.microsoft.com/sp

Does the query call any VBA code?

(I assume the problem occurs if you open the report directly from the
Database window, i.e. not through code.)

Does a compact, decompile, compact, compile sequence help? Details:
http://allenbrowne.com/recover.html

There is no vba code in the report or query.
OS is XP.
My version of office 2003
Where I work I can't update any service pack.
The computers that have 2002 have the problem.

I will try the decompile and get back.

 

[Tony Toews [MVP]]

There is no vba code in the report or query.

So this happens when the user starts up the database and immediately
runs the report and immediately exits. Nothing else? And no other
reports have this problem.

My version of office 2003
Where I work I can't update any service pack.
The computers that have 2002 have the problem.

If no service packs are installed then I doubt we can help you.
Chances are the problem has been fixed.

Tony