Re: A more elegant solution?
- From: "Tom Whitehouse" <admin@xxxxxxxxxxxxx>
- Date: Sat, 7 Jul 2007 21:49:31 +0100
This is easy. Put a lable or text box on the form, put (name).caption or (name).text where name is something like lblFormVariable or txtFormVariable etc (depending on which you use), then make the label or text box hidden by default so set visible to false.
This should solve the problem : )
"Bob Quintal" <rquintal@xxxxxxxxxxxxx> wrote in message news:Xns99669CAFCE9E3BQuintal@xxxxxxxxxxxxxxxx
"Laurel" <FakeMail@xxxxxxxxxxx> wrote in
news:#Rgn0jMwHHA.1204@xxxxxxxxxxxxxxxxxxxx:
I often want to display the value of a global variable in awhy go to all that trouble. Just put a label on the form or report
form or report. I need to do this via a function (can't just
display the variable itself, it seems). Instead of a bunch of
specific functions, I'd like to have a single
"fncDisplayGlobal()" function. I could create one with an
ever-growing SELECT statement in it, but is there a more
elegant way? Can I somehow pass in the name of the function
as a string and then magically turn it into the variable of
the same name? And then pass back the value?
and put the following code into the logical event
me.label.caption = variable.
--
Bob Quintal
PA is y I've altered my email address.
--
Posted via a free Usenet account from http://www.teranews.com
.
- References:
- A more elegant solution?
- From: Laurel
- Re: A more elegant solution?
- From: Bob Quintal
- A more elegant solution?
- Prev by Date: Re: Preventing duplicate record entries where two fields are invol
- Next by Date: Re: A more elegant solution?
- Previous by thread: Re: A more elegant solution?
- Next by thread: Re: A more elegant solution?
- Index(es):
Relevant Pages
|