Re: Naming Standard

From: Larry Linson (bouncer_at_localhost.not)
Date: 08/29/04 

Date: Sat, 28 Aug 2004 23:08:15 -0500

The most generally-accepted naming standard is the Reddick Naming
Convention, derived from the Leszynski*-Reddick Naming Convention for Access
2.0. It is documented in the _Access <versionnumber> Developers Handbook_,
by Litwin, Getz, et al, published by Sybex. In any case, I recommend that
serious Access power users and developers have a copy of that book -- Paul
Litwin told me there will be no Access 2003 edition, but the 2002 edition
should be fine for Access 2003 work.

   * I beg pardon if I misspelled this name.

Microsoft has something on this in the Knowledge Base, but I have not
checked lately to see if it is up-to-date. Googling on the name might lead
you to an online description.

  Larry Linson
  Microsoft Access MVP

"David" <anonymous@discussions.microsoft.com> wrote in message
news:220501c48d7b$c74d6b10$a301280a@phx.gbl...
> Is there a good link for a standard naming convention in
> Access?
>
> Microsoft says anything that is 64 characters or less.
> SQL says, no spaces. I'm beginning to have a lot more
> automation between tables, forms and queries and I am
> strugling with making sure I reference the exact name.
>
> Any assistance would be greatly appreciated.
>
> David

Relevant Pages

  • Re: Member Variables Naming Convention
    ... you get some people saying "developers should be free to express ... I also believe that using industry standards (i.e. the naming convention ... all the work of writing the standard docs and publishing them and maintaining ... "Dave Sexton" wrote: ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Member Variables Naming Convention
    ... you get some people saying "developers should be free to express ... I also believe that using industry standards (i.e. the naming convention ... all the work of writing the standard docs and publishing them and maintaining ... such a problem, but if you're program is ever touched by anyone else, it might be confusing to ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: template question
    ... "Iguana" skrev i en meddelelse ... That is their naming convention, and it is allright with me. ... Avoiding the Microsoft naming convention has one advantage though: ... your function the same way as some microsoft function that has been defined ...
    (comp.lang.cpp)
  • Re: inheritance ideas
    ... there is no reason to prefix all of ... > Microsoft naming convention. ... Actually, it's not just Microsoft. ...
    (comp.lang.cpp)
  • Suggested Microsoft way
    ... Lately I came to know that Microsoft is suggesting to go with underscore for ... naming convention for variables. ... you have any URL which tells the Microsoft suggested way on coding standard ...
    (microsoft.public.dotnet.framework.aspnet)