Problems Shutting Down Access XP

[Guest]

I had a problem that I thought was Crystal Reports related, but now I'm not so sure.

I am using Access XP and Crystal Reports 8.5. I am using a main form as a switchboard and calling different subforms. One subform has reports on it. These reports are written in Crystal. After calling most of the reports and trying to shut down Access, I am having to CTRL-ALT-DEL to close Access. There does not seem to be any particular common thread among the reports that don't cause this problem.

Initially I thought I needed to close out the Crystal Report with something to the effect of CrystalReport3.close or exit or set to nothing or something of that nature. I also went through the program and made sure I set all the db and rs back to nothing.

I noticed that after compacting, Access seemed to be trying to close and then reopen. It wasn't frozen - I could open the database back up, but to shut it down I had to CTRL-ALT-DEL.

I changed the docmd.quit to Application.quit after reading some posts on another site. After doing this I got excited because I thought it had solved the problem and then Access reopened!!!

So I opened the Windows Task Manager to be certain what was going on and sure enough Access shut down briefly and then reopened.

Does anybody have a solution for this problem? I have gone through many, many steps in the last few days, thinking this was a Crystal problem, because that's the only place it happened. I can provide the code that calls the Crystal Reports, if that will be helpful.

 

[TC]

Not sure if this will help, but:

There are some known issues with Access closing, but remaining on the
taskbar (and in the ctrl/alt/del task list), if you refer to a checkbox
control in certain ways. For example:

if me![chkMyCheckbox] then

The problem is that Access establishes a reference to the checkbox control,
instead of evaluating it's default Value property for true or false. The if
test works, but the control reference is not cleaned up, and Access won't
close properly. To fix this problem, use the Value property explicitly:

if me![chkMyCheckbox].Value then

or use True or False explicitly:

if me![chkMyCheckbox] = True then

or for ultimate peace of mind, and that fresh, natural feeling thoughout the
day, use both:

if me![chkMyCheckbox].Value = True then

HTH,
TC

I had a problem that I thought was Crystal Reports related, but now I'm not so sure.

I am using Access XP and Crystal Reports 8.5. I am using a main form as a

switchboard and calling different subforms. One subform has reports on it.
These reports are written in Crystal. After calling most of the reports and
trying to shut down Access, I am having to CTRL-ALT-DEL to close Access.
There does not seem to be any particular common thread among the reports
that don't cause this problem.

Initially I thought I needed to close out the Crystal Report with

something to the effect of CrystalReport3.close or exit or set to nothing or
something of that nature. I also went through the program and made sure I
set all the db and rs back to nothing.

I noticed that after compacting, Access seemed to be trying to close and

then reopen. It wasn't frozen - I could open the database back up, but to
shut it down I had to CTRL-ALT-DEL.

I changed the docmd.quit to Application.quit after reading some posts on

another site. After doing this I got excited because I thought it had
solved the problem and then Access reopened!!!

So I opened the Windows Task Manager to be certain what was going on and

sure enough Access shut down briefly and then reopened.

Does anybody have a solution for this problem? I have gone through many,

many steps in the last few days, thinking this was a Crystal problem,
because that's the only place it happened. I can provide the code that
calls the Crystal Reports, if that will be helpful.

 

[Guest]

This problem was due to basing my Crystal Reports on tables rather than queries. Queries create an indirect connection. Once I changed my reports to pull from queries I no longer had the problem. Just a note: I renamed the tables and named the queries based on the table name which eliminated having to make any changes to the reports themselves.