I have over two hundred toggle buttons on a form. Is there a way to write
"general" code rather than code each button that will turn the font red on the
button I turn on and turn the font back on the button I turn off?

I'm trying to save not having to code each button but have individual buttons
react to On and Off.

Thanks!

Rachel

Sel,

I looked through Forms, APIs and Modules and did not find anything referencing
my issue. Can you be more specific as to where to look.

Thanks!

Rachel


"Sel Short" <ss987610 (AT) hotmail (DOT) com> wrote

Hey, mister, thanks for wasting my time!!!

Why don't you mind your own business when you don't have anything constructive
to say.

Rachel


"Sel Short" <ss987610 (AT) hotmail (DOT) com> wrote

Sorry, lady, I though your post was a joke. Larry Linson, our resident MVP
sickboy, is always posting messages like yours.

To be frank, you really need to rethink what you are doing. Any
professional developer will tell you that the number of toggle buttons you
are using is absurd (thus the implication that your post was a "professional
joke.")

Sel

PS: Maybe if you explain what you hope to achieve with more than 200 toggle
buttons, something more can be suggested.


"Rachel" <rlaird (AT) penn (DOT) com> wrote

My name isn't Larry!

My original post was a legitimate request for help!

You're not only rude but ignorant!!!

Rachel


"Sel Short" <ss987610 (AT) hotmail (DOT) com> wrote

OK, Larry, you got me.


"Rachel" <rlaird (AT) penn (DOT) com> wrote

"Sel Short" <ss987610 (AT) hotmail (DOT) com> wrote

You should have told her to post a screenshot of her form on MitchKa's site.
Arvin and I are always looking for good designs.

Jayson

Rachel wrote:
Chuck's reply is correct. You will have to have the code called on an
event for each command/toggle button

You could do something like this...this is untested code but you should
get the general drift and you can modify it to suit your needs. It
basically writed all of the code for you if you want the code in each
toggke button.

Sub WriteToggleRoutine()
Dim sf As String
Dim f as Form
Dim c as Control
sf = "YourFormName" 'subtitute YourFormName with the form's bame.
Docmd.openform f,acdesing,,,,acHidden
set f = Forms(sf)

Open "Toggle.Txt" For OutPut As #1

For each c in f.controls
'loop through each label, combo, text, toggle
if ctl.ControlType = acToggleButton then
'let's say you want to call this on the onclick event
Print "Private Sub " & _
ctl.name & "_OnClick()"
Print chr(9) & "SetFontToRed"
Print "End Sub"
endif
next
Close #1
msgbox "Done"
End Sub

Now open up Toggle.Txt and paste it into the code. You want to have
this call the routine you are going to call in. Let's say the rootine
you are going to call is SetFontToRed. You could make that
Print chr(9) & "SetFontToRed(Me)"
or
Print chr(9) & "SetFontToRed(Me,ActiveControl)"

hen in your SetFontToRed sub you have the form name or the control name
that you called.
Private Sub SetFontToRead(frm As Form, ctl As Control)

Rachel,

Sel Short is, in fact, Don P Mellon, the resident troll in this newsgroup.
He's definitely unfond of MVPs, sometimes impersonates them, and always
tries to either belittle them or make them look bad.

I don't see that my response to your post actually made it to the server,
but I said that you could write DAO code to execute in the design view of
the Form to set the contents of the event property of those controls --
fairly simple code, and thus you won't have to manually enter the
information for each.

I also said that will be a pretty "busy" form, it won't be awfully
user-friendly, and maybe you should take another look at the design to see
if you can't group the functionality so you don't have so many toggle
buttons on the same form.

Larry Linson
Microsoft Access MVP



"Rachel" <rlaird (AT) penn (DOT) com> wrote

From your post, its not clear whether these are 200 stand-alone toggles, or
an option group with 200 toggles. But if the behaviour is such that turning
one "on" turns the prior button off, then it certainly sounds like an option
group.
If so, you can use naming conventions and the option group afterupdate event
to make this easy.
Name your buttons tog1, tog2, tog3.... up to 200. I am assuming the the
underlying toggle values correspond to their name, i.e. tog1 = 1, etc.
Declare a module level variable
Dim strPriorButton as string

In the afterupdate event of the option group(opgLotsaButtons) use something
like:
Me!("tog" & me!opgLotsaButtons).Forecolor = 255
If Len(strPriorButton)>0 then
Me!(strPriorButton).Forecolor = 0
End if
strPriorButton ="tog" & me!opgLotsaButtons


"Rachel" <rlaird (AT) penn (DOT) com> wrote