MS access coding standards.

[db2sysc]

ALl.

Is it possible to get MS ACCESS CODING STANDARDS?

TIA

[Scott McDaniel]

The same standards apply to Access as would apply to VB6 ... it's basically
the same language

--
Scott McDaniel
InfoTrakker Software
<db*****@gmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...

ALl.

Is it possible to get MS ACCESS CODING STANDARDS?

TIA

[Larry Linson]

<db*****@gmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...

ALl.

Is it possible to get MS ACCESS CODING STANDARDS?

Many of the Access self-study books have recommendations for coding
conventions. There is no "standards body" to "bless" an official standard.

"Have and use a naming convention" is one common recommendation. Probably
the most widely-used Access naming convention is the Reddick Naming
Convention. You'll find it described at Greg Reddick's website,
www.xoc.net/standards/default.asp.

I got a lot of hits when I googled on Reddick Naming Convention, so leading
to discussions of additional standards, too. I got several hits, too, on
"Access Coding Standards"

Larry Linson
Microsoft Access MVP

[Larry Linson]

"Scott McDaniel" <sc***@infotrakkerDELETEME.com> wrote in message
news:p_********************@comcast.com...

The same standards apply to Access as would apply to VB6 ... it's
basically the same language

Classic VB coding standards have never been as clean as Access -- there were
at least three different naming conventions for classic VB used just within
Microsoft.

Except for refugees from VB who brought their old habits along, by far the
most widely used and well known Naming Convention for Access is the Reddick
Naming Convention, www.xoc.net/standards/default.asp.

Larry Linson
Microsoft Access MVP

[David W. Fenton]

"Larry Linson" <bo*****@localhost.not> wrote in
news:dq6Ke.994$0d.282@trnddc09:

"Scott McDaniel" <sc***@infotrakkerDELETEME.com> wrote in message
news:p_********************@comcast.com...

The same standards apply to Access as would apply to VB6 ... it's
basically the same language

Classic VB coding standards have never been as clean as Access --
there were at least three different naming conventions for classic
VB used just within Microsoft.

Except for refugees from VB who brought their old habits along, by
far the most widely used and well known Naming Convention for
Access is the Reddick Naming Convention,
www.xoc.net/standards/default.asp.

I highly recommend this article for a very pertinent critique of the
reverse Hungarian notation that we've become accustomed to:

http://www.joelonsoftware.com/articles/Wrong.html

I think Joel is absolutely right about this one, though I haven't
yet altered my coding as a result.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Scott McDaniel]

You're correct, of course, guess I was thinking of more than just nameing
conventions. The old "Practical Standards for Visual Basic" from MS press
was more along the lines of what I was thinking of ... or perhaps, if you
want to do a LOT of reading "Code Complete" by McConnell.

"Larry Linson" <bo*****@localhost.not> wrote in message
news:dq6Ke.994$0d.282@trnddc09...

"Scott McDaniel" <sc***@infotrakkerDELETEME.com> wrote in message
news:p_********************@comcast.com...

The same standards apply to Access as would apply to VB6 ... it's
basically the same language

Classic VB coding standards have never been as clean as Access -- there
were at least three different naming conventions for classic VB used just
within Microsoft.

Except for refugees from VB who brought their old habits along, by far the
most widely used and well known Naming Convention for Access is the
Reddick Naming Convention, www.xoc.net/standards/default.asp.

Larry Linson
Microsoft Access MVP