Re: Hide/disable Close button

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: helenp (anonymous_at_discussions.microsoft.com)
Date: 12/23/04 

Date: Thu, 23 Dec 2004 10:47:44 -0800

Thanks, Immanuel. I'm still searching for the previous
messages on this subject. One thing we seem to be running
into is minor corruption creeping in when the app is
closed with the db still open. We'll be addressing this
by going to a distribution of copies of the front end as
soon as we get some things in place (we're still fixing
our network after an incompentent original setup), but
that may be a while. In the meantime, a macro attached to
the Exit button closes the db, then the app. We also had
some security issues with people going around the
custom .mdw, but this may be ok now that the database
container is hidden, so they have to close Access to
close the db.

I'm still learning Access programming, mostly on my own,
so I appreciate the help. This trial and error can kill
you! I'll try a phantom form, see if that does what I
need.

Helen

>-----Original Message-----
>
>Helen,
>
>What would be an example of problems created by users
clicking the "X" to
>close the app?
>Do you do some kind of housekeeping/maintenance routine
that you put in your
>customized "Close" button (i.e. what you refer to
as "closing the db")?
>
>You could have a form (i.e. just a dummy form) that you
open as a
>hidden/invisible form everytime the app is launched. Put
your closing
>routine on the On Close event of this form. This dummy
form will be always
>be open but invisible for the duration of the user's
session. When the user
>clicks "X", Access will close this invisible form and
the On Close event
>will fire.
>
>I use this phantom form all the time. It allows me to do
closing routine if
>necessary. But more than that, there are other benefits
such as declaring
>and holding global variables, and for performance reason
(i.e. the very much
>discussed "keeping a recordset open to enhance
performance").
>
>
>Immanuel Sibero
>
>
>
>"helenp" <anonymous@discussions.microsoft.com> wrote in
message
>news:20f401c4e86d$6feda0e0$a401280a@phx.gbl...
>> We're having ongoing problems with our db that may be
>> coming from people closing the application without
first
>> closing the db. I've programmed a big red EXIT button
on
>> the interface, but people ignore it and use the
familiar
>> close button on Access instead. Is there any way to
hide
>> or disable the tempting red X?
>>
>> Thanks,
>> Helen
>
>
>.
>

Quantcast