Re: Back color
- From: fredg <fgutkind@xxxxxxxxxxxxxxx>
- Date: Thu, 18 Jan 2007 13:52:10 -0800
On Thu, 18 Jan 2007 13:10:05 -0800, Klatuu wrote:
Thanks for the reply, Fred.
My response was based on your choice of words "poor coding". I will assume
your intent was not as disrespectful as it appeared. I see your posts often
and usually your answers are usually helpful.
I still am opposed to your constant use of literal values rather than
intrinsic constants. Why do you do that? Constants are a great way to make
your code easier to understand. Certainly almost everyone using VBA knows -1
is True and 0 is False, but it is still easier to read code with constants
rather than literal values. Taking it to extreme, would you rather see:
Me.txtFuzzball.BackColor = 65535
or
Me.txtFuzzball.BackColor = vbYellow
Sorry, but it is one of those pet peeves of mine.
Thank you for being out here helping those who have questions.
David,
I'm glad we're clear.
I don't quite follow you with your concerns regarding:
I still am opposed to your constant use of literal values rather than intrinsic constants. ....
Me.txtFuzzball.BackColor = 65535
or
Me.txtFuzzball.BackColor = vbYellow
in this thread.
For me, personally, as long as the 2 values were the identical color,
I would rather see vbYellow. I can visualize Yellow, but I have no
idea what 65535 as a color value looks like, and I certainly can't
remember that 16711680 is vbBlue.
Did I miss understand something in this regards?
--
Fred
Please respond only to this newsgroup.
I do not reply to personal e-mail
.
- References:
- Re: Back color
- From: fredg
- Re: Back color
- From: fredg
- Re: Back color
- From: Klatuu
- Re: Back color
- Prev by Date: Labels Report and Page Breaks
- Next by Date: dynamic reporting
- Previous by thread: Re: Back color
- Next by thread: Re: Back color
- Index(es):