Re: Double-click to Open .mdb annoyance

Sorry, I haven't got any other ideas. I know there was a problem in Access
97 that could cause this (see http://www.mvps.org/access/bugs/bugs0005.htm
at "The Access Web"), but I don't think it's still an issue with Access
2003. (although there's no harm trying the suggesions on that page!)

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Rich K" <RichK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:66A0B36C-DAC5-40C5-BFB7-61F07AC3AD74@xxxxxxxxxxxxxxxx
No, I tried both the Application.Quit and the Docmd.Quit with various
arguments and yet the msaccess.exe process continues to run in the
background.

This has turned into a totally different problem than I originally posted,
and more important than I thought. I don't like the idea of leaving
unintended processes running on client computers eating up resources.

Rich

"Douglas J. Steele" wrote:

Does Application.Quit work?

Note that the Quit method takes one of the following arguments as a
parameter:

acSaveYes (Default) Saves all objects without displaying a dialog box.
acPrompt Displays a dialog box that asks whether you want to save any
database
objects that have been changed but not saved.
acExit Quits Microsoft Access without saving any objects.

Note that this refers to changes to database objects (i.e. Forms,
Reports,
Macros, Modules, etc), not to changes to data.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"Rich K" <RichK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:614769F5-CBFD-4069-98A8-8A7B8029428C@xxxxxxxxxxxxxxxx
Douglas,
I think I figured out the issue. I exit the database with a docmd.quit
behind a command button on a form. This closes the database but keeps
the
process msaccess.exe is still running, which is probably interferring
with
the next start up.

A quick search has revealed others have had the issue also. Is there a
process for quitting an application (.adp) and also ending the
msaccess.exe
process?

Thanks,
Rich

"Douglas J. Steele" wrote:

Rather than rebooting the machine, try opening the Task Manager.

Look first on the Applications tab, just in case your database is open
there. (Try the "Switch To" button if it is). Failing that, look on
the
Processes tab for an instance of MSACCESS.EXE and end it.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Rich K" <RichK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D092961D-8080-4BAC-80F6-91774FCA4A72@xxxxxxxxxxxxxxxx
Recently when I've been working on .mdb files double clicking
directly
on
the
file does not open the file in access, yet the .ldb file is created.
I
can
open Access first and then the file, but it's a royal pain. If I
try
to
open
the file by double clicking first and it does not open, I end up
having
to
reboot the machine so that I can open the file exclusively to edit
it.
Does
anybody have any resolution to this issue?

I work on the same machine with .adp files and they do not seem to
have
this
issue.

I'm using Access 2003 SP3 w/ Windows XP SP 3








.

Loading