.....Hey Steve Schapel...!

  • Thread starter Thread starter Popparod
  • Start date Start date
P

Popparod

.....I got it working.....!!!!!

.....On my Members Form.....I changed the Street Text Box name to
"txtStreet"....

.....I wish the HELP files would kinda clarify things a little
differently......

.....I guess NEVER name your control to the Field it's bound to....is that
right.....?

.....I guess I'll go back thru and Rename all of them to
"txtWhatever"..."cboWhatever"....

.....I'm sure glad you guys are there to Help out....I re-read your messages
and it dawned
on me thats what you were saying.....
 
Popparod said:
....I got it working.....!!!!!

....On my Members Form.....I changed the Street Text Box name to
"txtStreet"....

....I wish the HELP files would kinda clarify things a little
differently......

....I guess NEVER name your control to the Field it's bound to....is
that right.....?

....I guess I'll go back thru and Rename all of them to
"txtWhatever"..."cboWhatever"....[snip]
Click to expand...

Unless I am using an expression as the ControlSource I *always* name my controls
the same as the field they are bound to and have never had an issue with it.
 
Popparod wrote
[]
....I guess NEVER name your control to the Field it's bound to....is that
right.....?

....I guess I'll go back thru and Rename all of them to
"txtWhatever"..."cboWhatever"....

....I'm sure glad you guys are there to Help out....I re-read your messages
and it dawned on me thats what you were saying.....
Click to expand...


That is certainly a safe rule to follow, but it's more work
than necessary. There won't be a conflict unless you refer
to a control in a control source expression.

My rule is to ignore the name of controls UNTIL I refer to
it in a control source expression or in VBA code (including
creating an event procedure). There's a bit of "not really
required" in the way I do It, but I hate writing
expressions/code where it's unclear whether I'm referring to
a control or a field. I also have an aversion to writing
expressions/code that includes names like Text27.
 
.....Rick....You said.....
.......Unless I am using an expression as the ControlSource......

.......The whole "Control Source" thing has eluded me for so many
"Access filled computer code dreams" for so long....I feel like a kid
in a candy shop now that I got it working.......

.....You guy's just make it seem SO easy........

.....Now that we got that figured out.....it's on to VBA Code.....!

.....Subs and Functions and imbedded Procedures...
.....these are the things to keep my mind reeling.....
.....typing in code...then to see if things work....
.....it'd be alot easier if I had a damn book...
 
Popparod,

Like Rick, I always name form controls the same as the field they are
bound to. This is not the problem here. The problem here is naming a
control the same as the name of a field which the control is *not* bound
to. When you enter an expression in the Control Source property of a
textbox, then that textbox is not bound to any field in the form's
record source. It is in these circumstances that the control should not
have the same name as a field.

In the example that we were discussing in the earlier thread, I
presented you with 2 options. Maybe this is where the confusion came
in. One option was to create the calculated field in a query, and then
base the form on this query. If you had done it that way, the control
on the form would be bound to a field. The question of terminology
comes into it too, as I think you were using the word "query" to refer
to an expression, so we had a cross-over of meaning there too.

By the way, looking back over the previous thread, I notice there were
two posts from me where I mentioned that the calculated control should
not have the name of the field :-)

Anyway, I am very pleased to know that you have made progress.
 
....You said.....

By the way, looking back over the previous thread, I notice there were
two posts from me where I mentioned that the calculated control should
not have the name of the field :-)

......I didn't quite understand what you meant by that then....
but I do ....NOW( )......"a little code humor"


.......Thank you so much again for you Patience.......!
 
Back
Top