[AccessD] Is there a simpler way?
John Colby
jwcolby at gmail.com
Wed Jul 13 18:04:35 CDT 2022
Affect vs effect. The possessive It is one I absolutely know because my
wife is an English major proofreader, but I still have to stop and correct
it half of the time. It affects me constantly and the effect is dire...
when Arthur is reading my posts.😁😎
On Wed, Jul 13, 2022 at 5:56 PM Susan Harkins <ssharkins at gmail.com> wrote:
> I'm so sorry -- I thought I was replying in OT -- but the subject does seem
> to have a bit of an audience here. It's kind of universal.
>
> Thank you for not blasting us and I'll make sure I'm replying in OT going
> forward!
>
> Susan H.
>
>
> LOL you can say that again.
>
> Lately, I've picked up a nasty habit of typing "Think" when I mean to type
> "Thing" and "Thing" when I wanted "Think". I'm doing it with "send" and
> "sent" as well. Somehow the wires have gotten crossed.
>
> I've also noticed that I'll fill in words when reading/proofing something,
> but when I look at it later, the fact that a word is missing jumps right
> out.
>
> The joys of getting older...
>
> Jim.
>
> -----Original Message-----
> From: AccessD On Behalf Of Susan Harkins
> Sent: Wednesday, July 13, 2022 1:25 PM
> To: 'Access Developers discussion and problem solving'
> <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] Is there a simpler way?
>
> I think more people know these rules than you might think. The problem
> isn't
> remembering the rule--it's applying it. Rocky calls this phenomenon brain
> farts. We all experience this problem, and some of us more than others.
>
> Proofing your own work is also difficult. It's a physiological thing -- not
> laziness or ignorance. Tina, as careful as you are, you wrote "toe" instead
> of "to" in one of your posts to us on this subject. I know how careful you
> are. I'm not pointing that out as ridicule, but as an example of how even
> the best of us, which you are, make mistakes and don't catch them.
>
> I sent in an article last week with the term delimiter scattered about. The
> editor caught one that I'd spelled "dimeter" -- I blame that one on
> AutoCorrect, but I didn't catch it in my last edit.
>
> This is why I have editors. It's real. In the end, the frustration we feel
> only hurts us -- the writer is totally and blissfully unaware.
>
> Susan H.
>
> -----Original Message-----
> From: AccessD <accessd-bounces+ssharkins=gmail.com at databaseadvisors.com>
> On
> Behalf Of Arthur Fuller
> Sent: Tuesday, July 12, 2022 8:50 PM
> To: Access Developers discussion and problem solving
> <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] Is there a simpler way?
>
> >> Clarity is it's own reward.
> Reverting to another thread, this is an example of the incorrect use of
> "it's". In this context, it ought to have been "its". The rule is simple:
> expand any occurrence of "it's" to "it is" and see if the sentence still
> makes sense. If not, you're using the wrong one.
>
> On Tue, Jul 12, 2022 at 8:36 PM Rocky Smolin <rockysmolin2 at gmail.com>
> wrote:
>
> > Yes. Ugly. But in compensation it is perfectly understandable,
> > readable, maintainable. By any programmer. And five years from now you
> > won't be trying to figure out what this code does as opposed to 'clever'
> code.
> > Clarity is it's own reward.
> >
> > r
> >
> > On Tue, Jul 12, 2022 at 3:46 PM John Colby <jwcolby at gmail.com> wrote:
> >
> > > I need a text enum (colors to be specific). Enums are longs. Sigh
> > >
> > > Public Enum enumVBColors
> > > Black = vbBlack
> > > Red = vbRed
> > > Green = vbGreen
> > > Yellow = vbYellow
> > > Blue = vbBlue
> > > Magenta = vbMagenta
> > > Cyan = vbCyan
> > > White = vbWhite
> > > End Enum
> > >
> > > Function fColor(intColor As enumVBColors) As String
> > > Select Case intColor
> > > Case enumVBColors.Black
> > > fColor = "Black"
> > > Case enumVBColors.Blue
> > > fColor = "Blue"
> > > Case enumVBColors.Cyan
> > > fColor = "Cyan"
> > > Case enumVBColors.Green
> > > fColor = "Green"
> > > Case enumVBColors.Magenta
> > > fColor = "Magenta"
> > > Case enumVBColors.Red
> > > fColor = "Red"
> > > Case enumVBColors.White
> > > fColor = "White"
> > > Case enumVBColors.Yellow
> > > fColor = "Yellow"
> > > End Select
> > > End Function
> > >
> > > Does the trick but DAMN! I can use these text strings as colors in
> > > the HTML tags. But DAMN! I hate ugly and this is just ugly.
> > >
> > > Let the slappin' commence.
> > >
> > > --
> > > John W. Colby
> > > Colby Consulting
> > > --
> > > AccessD mailing list
> > > AccessD at databaseadvisors.com
> > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > Website: http://www.databaseadvisors.com
> > >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
>
>
> --
> Arthur
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
--
John W. Colby
Colby Consulting
More information about the AccessD
mailing list