A2K Application.Quit won't - reference MDA libraries

Greetings,

I have an application which has recently gone from being one big piece
of front-end code to being three, i.e. an mdb A that references an mda
B and an mda C. (For what it's worth, in the interest of complete
disclosure, mda B also references mda C).

This application has always closed in the mvps time-honored method of
calling Application.Quit on the Unload event of the switchboard.

Problem is, now the db closes (the ldb on the back end disappears), but
Access doesn't shut down, and the ldbs on all three front-end projects
are still there.

Before you answer, please consider that
* DoCmd.Quit doesn't do any better, and none of the arguments change
the outcome
* I've read every thread on this forum containing the words
"application" and "quit", to no avail--which hopefully means there's an
easy answer!
* The two-three references to "quit" "access" in the MSKB don't apply
* I am explicitly closing every object reference prior to invoking said
quit method

So I guess I'm asking, can anyone tell me how to "close" an mda
reference in such a way that the Application will Quit? Or is there
something else I've missed, and I'm asking the wrong question?

Thanks for your time & consideration.

re: A2K Application.Quit won't - reference MDA libraries

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

What version of Access? There was a reported bug about "unable to close
Access" in which one of the solutions was to ensure that all checks of
Boolean values and CheckBoxes be changed from this:

If BooleanVariable Then ...

or

If CheckBox Then ...

To this:

If BooleanVariable = True Then ...

or

If CheckBox = True Then ...

Also, make sure the DoCmd.Quit is in the .mdb file not in the .mda
files.
--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQnAFHIechKqOuFEgEQK5NQCfWzIzpRRF23XRhsQ84fx8lV GPISYAoIMw
6tLGi+SE9gNutVgTTu2ns8IG
=vqzx
-----END PGP SIGNATURE-----


downwitch wrote:[color=blue]
> Greetings,
>
> I have an application which has recently gone from being one big piece
> of front-end code to being three, i.e. an mdb A that references an mda
> B and an mda C. (For what it's worth, in the interest of complete
> disclosure, mda B also references mda C).
>
> This application has always closed in the mvps time-honored method of
> calling Application.Quit on the Unload event of the switchboard.
>
> Problem is, now the db closes (the ldb on the back end disappears), but
> Access doesn't shut down, and the ldbs on all three front-end projects
> are still there.
>
> Before you answer, please consider that
> * DoCmd.Quit doesn't do any better, and none of the arguments change
> the outcome
> * I've read every thread on this forum containing the words
> "application" and "quit", to no avail--which hopefully means there's an
> easy answer!
> * The two-three references to "quit" "access" in the MSKB don't apply
> * I am explicitly closing every object reference prior to invoking said
> quit method
>
> So I guess I'm asking, can anyone tell me how to "close" an mda
> reference in such a way that the Application will Quit? Or is there
> something else I've missed, and I'm asking the wrong question?
>
> Thanks for your time & consideration.
>[/color]

re: A2K Application.Quit won't - reference MDA libraries

It's Access 2000 (in the thread title). And yes, I saw that bug--an
Access 97 bug--but that's not the problem. And no, the quit call is in
the principal mdb.

Thanks for taking a shot, anyway.

I've checked and rechecked all my references, stepped through code, and
managed to make Access drop the ldb on the mdb front-end file, but it's
still holding on to the other two, and therefore not closing.

Very, very frustrating. I'll keep at it though...

re: A2K Application.Quit won't - reference MDA libraries

Just a follow-up for anyone else who may read this now or forever...

I still haven't found a way to get rid of the locking files on mda
libraries. But by converting them to mde files--annoying
mid-development, but otherwise harmless--Access magically quits. So
it's a solid workaround.