Hi Richard, so fortunate to be one of your Silver Members. I so much better understand now how to use a Bang vs Dot. I posted a question/error in the form that has remained unanswered. It had to do with referencing a control on a subform. I believe I may have figured the root of this error myself. How about if you have a subform in a tab control, how do you make reference to a control on any one of those tab control pages?
Yeah there are a bunch of Forum posts I still have to read. I spent the last two days setting up my new laptop since my dog wrecked my last one. I couldn't type. LOL. As far as a subform in a tab control goes, don't use tab controls. They're evil. 599cd.com/Evil
@@599CD...now you tell me 😃. I'll need to redo a central part of my database but then again you mention tab controls are for novice. I would like to think of myself, of course under your tutelage, now a bit beyond that. Do I remember a Tech Help video you mentioning sub form management by VBA?
Fine for beginners and extremely convenient, but for the advanced and for best speed, don't use the bang operator. It has late-bound performance issues. Best performance is achieved by referring to the field using the full dot notation discussed at 2:40, as cumbersome as that is.
With Me .FirstName.Value End With Worked every time for me, just don't use reserved word. Why do they have .Value? Don't get me wrong, appreciate your instructions,. Will put into practice !
Me. and .value are superfluous. You don't NEED them, but it's not WRONG to use them. FirstName and Me.FirstName and Me!FirstName are all technically the same thing. The only time you NEED Me is if you're referring to properties, like Me.Caption FirstName.Value is the same as FirstName. .Value is the default property for a field.
Even when referring to properties, Me isn't necessary. Only time I've ever used Me in my 30 years of VB/VBA is when wanting to pass the current form as an argument to a sub/function.
@@599CD Hey - I do like your videos, by the way. Here's a puzzle: Put a control on a continuous form that shows the number of records in the current view. Sounds simple - but what about when the filter returns no records...try it. (This is useful to test if the form needs to be requeried). Clock starts....NOW
Very nice Mr.Richard Rost.
Thank you kindly
Hi Richard, so fortunate to be one of your Silver Members. I so much better understand now how to use a Bang vs Dot. I posted a question/error in the form that has remained unanswered. It had to do with referencing a control on a subform. I believe I may have figured the root of this error myself. How about if you have a subform in a tab control, how do you make reference to a control on any one of those tab control pages?
Yeah there are a bunch of Forum posts I still have to read. I spent the last two days setting up my new laptop since my dog wrecked my last one. I couldn't type. LOL. As far as a subform in a tab control goes, don't use tab controls. They're evil. 599cd.com/Evil
@@599CD...now you tell me 😃. I'll need to redo a central part of my database but then again you mention tab controls are for novice. I would like to think of myself, of course under your tutelage, now a bit beyond that. Do I remember a Tech Help video you mentioning sub form management by VBA?
599cd.com/Vehicle - extended cut - SourceObject property
Great Help sir. Thx
Most welcome
Very Helpful! 👍
Glad to hear that!
Very interesting 👌
Thanks
Fine for beginners and extremely convenient, but for the advanced and for best speed, don't use the bang operator. It has late-bound performance issues. Best performance is achieved by referring to the field using the full dot notation discussed at 2:40, as cumbersome as that is.
While that may be true, you're talking microseconds. :)
So also refering to form object do I need to use bang?
Like Me!txtFirstName?
What are the collection items within Me. (for instance, in a form)?
The form's properties like Caption, Name. Google for a full list.
Dear sir, please release access vb videos
Here you go: 599cd.com/IntroVBA
With Me
.FirstName.Value
End With
Worked every time for me, just don't use reserved word.
Why do they have .Value?
Don't get me wrong, appreciate your instructions,. Will put into practice !
Me. and .value are superfluous. You don't NEED them, but it's not WRONG to use them.
FirstName and Me.FirstName and Me!FirstName are all technically the same thing.
The only time you NEED Me is if you're referring to properties, like Me.Caption
FirstName.Value is the same as FirstName. .Value is the default property for a field.
Even when referring to properties, Me isn't necessary. Only time I've ever used Me in my 30 years of VB/VBA is when wanting to pass the current form as an argument to a sub/function.
exclamation mark for us Brits. :-)
Indeed!
The dot notation becomes useless especially when using recordset. Bang is the bang. Lol
Bangin'
He sounds sooo angry.
It was before lunch, OK? GIVE ME A BREAK!!!! :) LOL
@@599CD Hey - I do like your videos, by the way. Here's a puzzle: Put a control on a continuous form that shows the number of records in the current view. Sounds simple - but what about when the filter returns no records...try it. (This is useful to test if the form needs to be requeried). Clock starts....NOW