Acc2002 not closing properly?

[bradcccs]

Access 2002 (XP) on Windows 2000 Pro

After using (or designing within) a database, and exiting Access, it (Access) will not start again.

No error messages occur on db close.
If you access the Task Manager, MSAccess still exists as a process.

If you "End Process" on the offending MSAccess process, then Access will operate correctly.

I suppose this is not so much a problem as an annoyance.

I have searched (to the best of my ability) this forum / MS support / and Google etc for the solution. Have updated OS and Office XP from MS update service.

I now turn to the forum experts for help.

Thanks in advance.

Brad.

 

[Rich]

Do you have more than one version installed?

 

[bradcccs]

No.

Only Access 2002 SP-1. (10.3409.3051) with Office Suite

None of the other Office Progs give me any trouble.

I do however have the developers kit installed if that gives you any leaders.

Brad

 

[Jeff Bailey]

Don't really know if this applies to A2002 but it has been reported (frequently) that in earlier versions, if you create an object (eg a recordset) and do not explicitly close/destroy it yourself then Access can refuse to close.

Also, I seem to recall a problem with testing for True under some circumstances (I think it's related to checkboxes, but I'm not certain) ...

If chkMyBox then

can cause a problem while

If chkMyBox = True then

is OK

HTH

 

[bradcccs]

Jeff,

I think you may be on the right track.

I may not be able to blame MS after all.

I have just finished some time consuming investigation, and it appears to me that the problem only arises if I access a particular form during the database use.

And of course . . . . it is probably the most used form.

The form is used to establish a set of filters for a query, with the results being displayed in a datasheet style subform.

I have ran the query seperately (without the form filters) and the problem does not occur.

Thus the problem seems to be related to the form (or its objects) as you suggested.
The form includes buttons / option buttons / combo boxes (the works). The only thing it does not have is a check box.

I renamed the form and activated it.

When prompted for Forms!FormName.FieldName due to the renaming of the form, if I select "Cancel" the form opens (with no data), but the problem does not occur.
If I activate the renamed form, but select "OK" to the forms!.. prompt, the form opens (again with no data) and the problem does occur.

I will continue to investigate, but any further pushes in the right direction will be greatly appreciated.

Brad.

 

[Jeff Bailey]

I can only guess at the situation, of course, but it sounds as if, if it were my problem, I'd be removing stuff from the form bit-by-bit to try and isolate what causes the difficulty.

Good luck.

 

[bradcccs]

Jeff,

was doing exactly that while you were posting.

Progress report:

I have removed all objects from form (and code behind objects). Mind you I did that step by step to try to find the offender.

Problem still occurs. Have discovered it is actually the datasheet subform that causes the error.

I am looking into that now.

Eyes heavy - Temper high. Good combination.

Brad.

 

[bradcccs]

Well I'll be...

I have a text box on the subform with a simple if statement:
=IIf([Tbl_Docket.DocInOut]=1,"In","Out")

This text box is "Conditionally formatted" for back colour on result
ie: if "In" backcolour = green / if "Out" backcolour = red

If I remove the conditional formatting, the problem does not occur.

Any explanation or work around would be hugely appreciated.

This feature (In & Out being highlighted different) is one that my client is wrapped with.

Brad


-edit-


Problem fixed. Thanks to Jeff for his interest and hints. I was sure it was an XP issue.

Workaround: Conditional format statement now based on a numerical outcome, not text. Works great. - Does not format as quickly, but certainly does not lock access out.

 

[Jeff Bailey]

Well done. Another 'oddity' noted for future reference.