Re: The use of underscore characters in field naming conventions

Can't use Ctrl-Left Arrow or Ctrl-Right Arrow to do what?

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)



"CAD Fiend" <pelampeREMOVETHECAPS@xxxxxxx> wrote in message
news:42C1D826.193B91E2@xxxxxxxxxx
> Gotcha. But one thing about camel case is that you can't use the CTRL
> Left
> Arrow or Right Arrow on the keyboard when all of the text is together like
> that.
>
> "Douglas J. Steele" wrote:
>
>> There's really no right answer: naming conventions are just that,
>> conventions. (other than no spaces: few, if any, argue that spaces are
>> okay!)
>>
>> I personally prefer "camel case": using CapitalLetterToSeparateWords.
>>
>> --
>> Doug Steele, Microsoft Access MVP
>> http://I.Am/DougSteele
>> (no e-mails, please!)
>>
>> "CAD Fiend" <pelampeREMOVETHECAPS@xxxxxxx> wrote in message
>> news:42C1CB4C.B08ABB71@xxxxxxxxxx
>> > Hello,
>> >
>> > What is the proper naming convention for naming fields? Some people
>> > will use underscores between the key words, some just use caps. I
>> > believe that you also should not us spaces. Is that correct? What
>> > about
>> > for table names and such? Does the same practice apply?
>> >
>> > TIA.
>> >
>> > Phil.
>> >
>


.

Relevant Pages