Re: Microsoft Access, Double Data Entry and breaking the Normalization rule
- From: "David W. Fenton" <XXXusenet@xxxxxxxxxxxxxxxxxxx>
- Date: Thu, 31 May 2007 15:12:31 -0500
"hippomedon@xxxxxxxxxxxxxx" <hippomedon@xxxxxxxxxxxxxx> wrote in
news:1180558157.618085.168340@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:
Interesting question. For me, it's always finding a balance
between
having a variable name that is short and easy to type (for queries
and VBA code) and having one that is too short to be recognizable.
Intellisense removes the need for most of the typing.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.
- References:
- Microsoft Access, Double Data Entry and breaking the Normalization rule
- From: hippomedon@xxxxxxxxxxxxxx
- Re: Microsoft Access, Double Data Entry and breaking the Normalization rule
- From: DavidB
- Re: Microsoft Access, Double Data Entry and breaking the Normalization rule
- From: hippomedon@xxxxxxxxxxxxxx
- Microsoft Access, Double Data Entry and breaking the Normalization rule
- Prev by Date: Re: Microsoft Access, Double Data Entry and breaking the Normalization rule
- Next by Date: Re: Main form saving when click on subform??? A97
- Previous by thread: Re: Microsoft Access, Double Data Entry and breaking the Normalization rule
- Next by thread: Recordset question - strategy needed
- Index(es):
Relevant Pages
|