[AccessD] Open a combobox on entering it

Steve Schapel miscellany at mvps.org
Mon Jul 2 14:15:33 CDT 2007


I agree 100% with your assertions here, A.D.  For myself, I *always* 
adopt the naming convention of using the same  name for a bound control 
as the name of the field it is bound to.  And of course, I always ensure 
that an unbound or calculated control is *not* named the same as a field 
in the object's record source.  I know of no reason why this practice 
could cause a problem.

Regards
Steve


A.D.TEJPAL wrote:
> Naming of Bound Controls On Forms / Reports
> (Visa Vis Record Source)
> ==================================
> 
> Arthur,
> 
>     You need not feel apprehensive about your style of letting the name of pure bound controls remain the same as that of pertinent field in the record source.
> 
>     There is no evidence that naming a pure bound control same as its control source leads to any problem. Following postulation appears to hold good:
> 
> ====================================
>     1 - An unbound or calculated control should not have its name identical to any of the fields contained in the record source. 
>     2 - At the same time, it is perfectly Ok if the name of a pure bound control is the same as its control source, which of course is one of the fields in the record source.
> ====================================
> 
>     If any members of the forum would like to disagree, the reason may kindly be posted along with concrete evidence supporting it. It might be desirable to clear the picture for a large number of access users, who might feel somewhat over-whelmed by the universal assertion that no control should carry the same name as that of a field in the record source.
> 
>     What needs to be emphasized is that on a report or bound form, naming of calculated or unbound controls the same as the name of a field in the record source, could be a recipe for disaster, virtually equivalent to creation of imposter controls and should never be done.
> 
>     On the other hand, it should be perfectly all right to name pure bound controls the same as the record source field that serves as control source. In fact it could be the preferred practice, distinguishing such controls from others, which should carry a prefix like Txt or Cbo etc.
> 
>     Unfortunately, quite often, advice given in access forums makes a flat recommendation against naming of controls same as field names, without explicitly clarifying that the precaution is applicable to other than pure bound controls.
> 



More information about the AccessD mailing list