Rollover on Form Button

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I was wondering if MS Access has the ability to allow rollovers on buttons.
Here is my issue... I have 22 command buttons on a form that run a variety of
different queries. I want the user to be able to get a detailed description
of what each button does. The description that I want is too long to put in a
text box and thus too long to actually have the command button say that as
well.

My current solution is that I put a "?" button next to each query cmd
button. So that the user can click on that and it pops up a text box with a
detailed explanation. This works but is not exactly what I want. This causes
my form to have way too many cmd buttons. I would like the user to be able to
put the mouse on the button and it pop up a description without clicking on
anything.

Is this possible?
 
As an alternative, I suggest having a listbox with all of your query names
listed and a single button. Choose the query from the list then hit the
button that executes the query. On my website (www.rogersaccesslibrary.com)
are two small sample Access databases which illustrate this:
"ChooseReportFromList.mdb" and "ChooseReportFromList2.mdb"

ChooseReportFromList.mdb shows how to use the Description property of the
query to display a description. The sample illustrates it with Reports, but
it works much the same for queries. ChooseReportFromList2.mdb has a more
advanced form and actually shows how to use queries as well.

--
--Roger Carlson
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L
 
Try using the 'Mouse Move' event of the cmd button. You
can also clear the detailed message with the 'Mouse Move'
event of the detail (or other) section.
 
This may be overly simplistic, but how long does your
description need to be? If it's 255 characters or less,
why not use the ControlTip Text property of the command
button? That's long enough to show:

This is a tip. This is a truly lovely tip,
that answers the eternal question of life,
the universe, and everything! This tip,
which is obviously lovlier than any tip in
history, has been very carefully considered
by Deep Thought, is 42.

By my count, that 240 characters, including returns.

Keep in mind ControlTips don't wrap, so you'd need to put
in your own returns.

HTH!
 
The ControlTip solution is good, if you can use it.

The StatusBarText could also be useful; you probably can set it so that the
status bar has someting relevant when a button has focus.

I don't know how much work it is to use the "Help Context Id" but it might
be worth the extra work. If you write a help file for the application, then
it is probably quite easy to connect the buttons with the help using Help
Context Id; especially if you write the help file with an understanding of
use of Help Context Id too. I don't know anything about use of help files
and Help Context Ids using Access, except I know there are articles about
that. I have a couple of articles about HTML Help, but one of them is for
use with C++. If it does help, see my "Introduction to HTMLHelp" (not C++
specific) at:

http://simplesamples.info/Miscellaneous/HTMLHelp.php
 
Back
Top