|
Home > Archive > MS Access database support > April 2006 > Re: Microsoft's choice to default form textbox names to related table
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: Microsoft's choice to default form textbox names to related table
|
|
| Tim Marshall 2006-04-06, 1:34 pm |
| MLH wrote:
> Generally, I do not monkey with renaming controls on forms
> whose name, by default, matches the name of their related
> table fields.
<snip>
I didn't follow what you were trying to say in the rest of your post,
MLH, but the above definitely caught my eye.
I personally make it a habit to definitely rename bound controls to a
standard naming convention. Otherwise you end up with a lot of #Name!
type errors when trying to perform actions or procedures on controls. I
always advise newbies to do the same and tell them it's never good
practice to do what you describe above unless there is no coding
whatsoever connected with the form/report.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me
| |
| Tim Marshall 2006-04-07, 8:27 pm |
| MLH wrote:
> I tend to agree with you. Would be nice if we could set a low-level
> option specifying our desired control naming convention to A97.
Agreed. Or even if it just didn't name it the same as the blinking
controlsource!!! 8)
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me
|
|
|
|
|