Re: Can't find old post - Command Button Visible

I will add the Case Else as you suggested. When I put the vbOKOnly on the
last part of the Case, it created a compile error. I wasn't sure that was
part of the code so I deleted it and it worked ok. Does this have anything
to do with the Library 3.6 compile problems I've had? It took me the longest
time to finally find information regarding checking that library in the tools
area and it fixed the compile problems I was having that I had looked for for
hours and hours.... and hours... and... well, you get the picture.

Re: the Quit. I will take the "close form" out of the macro on the command
button that I'm using now. I have the database compacting on closing, so it
takes a while to close. (or seems to) Any thing I can do to cover that
"pause" . It's not a very clean close.

Thanks for all your help. It has been a learning experience on this database
since I've had to search out code to do things I haven't needed to do on
previous databases. Thank goodness for this Community forum, and all you
that help!!

Connie

"Joan Wild" wrote:

> "Connie" <Connie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:B2087576-D391-4ADA-B4D8-CF02384CB502@xxxxxxxxxxxxxxxx
> > Joan, Thank goodness you found my post! Thanks for the tip.
> > If you look at the post I posted, you'll see I was using my name
> > crifenburg
> > ....but look closely... <blush> I spelled my own name wrong!! So OF
> > COURSE
> > IT WASN'T SHOWING ME THE BUTTONS!
>
> That's a good reason to include a Case Else statement to cover off cases
> that don't fit.
>
> Case Else
> MsgBox "You are not registered...", vbOKOnly
> End Select
>
> That would have caught your error.
>
> > I had one more thing that confused me, how to exit the database with using
> > the Wizard Switchboard Exit application. I made a macro with "Close Form"
> > and "Quit" and that shuts down the database ok... but is there a better
> > way?
>
> I assume you have a button on your main menu form to exit the application?
> And that is where you are using this macro?
>
> If so, your macro just needs to use the Quit action (close form isn't needed
> as that will happen anyway when you quit).
>
>
> --
> Joan Wild
> Microsoft Access MVP
>
>
>
.