What is difference between (Bang) and Dot ? VBA

[Hossein]

Hi guys

I have some simple question

1) What is difference between (Bang) and dot ? for example Me!Combobox vs Me.Combobox

2) What is difference between Me.Combobox vs Me.Combobox.value vs Combobox

3) What is difference between [Forms]![SampleForm]![Combobox] vs Me!Combobox

4) Do you have good source as a book or video course training in order to VBA in access and writing query ? (Related to query i am using access query wizard or some times, SQL assistant as a addins software that is great)

[June7]

1. Dot provokes VBA intellisense popup tips

2. Nothing because Value is default property for data controls. Omitting explicit reference to form will still work but won't get intellisense.

3. If the first syntax you show is behind the referenced form, then there is no difference. The first syntax can be used in queries. Me. and Me! can only be used in VBA

4. I am sure there are many but I don't actually have one. This question has been asked many times. Here is one https://www.accessforums.net/showthread.php?t=55379

[Uncle Gizmo]

2. Nothing because Value is default property for data controls. [/URL]

"Value" is indeed the default property and you seldom need to use it, however there is one area I have discovered that you do need to use it see my post here:-

https://www.niftyaccess.com/tempvars-value-error/

Sent from my Pixel 3a using Tapatalk

[Micron]

there is more to 1 then that.
Bang provides late bound access to the default member of the object that precedes it by passing the name value of what follows it. If we use Me as an example, the default member of Me is the controls collection, thus Me!txtDept will work IF txtDept is a control on the form referenced by Me. Me.txtDept is an explicit reference to the parent object and its child member and is not late bound. Therefore, if we misspell the control name txtbox, Me.tttextbox will be caught when you compile the code or attempt to run it. Me!tttextbox will not raise an error until there is an attempt to execute that line of code. I NEVER use Me!

That is not a complete treatise on the subject; e.g. I have not thought about why ! is the correct (only?) method when it comes to certain recordset references such as when referring to a recordset field by name. That does not include referencing the recordset field via the Fields collection.

Regarding 3, it should then be apparent by the forgoing that I would not use [Forms]![SampleForm]![Combobox] either.
It would be [Forms]![SampleForm].[Combobox]
So why not [Forms].[SampleForm].[Combobox]? I don't know. It is just one of those things that you (I) learn is the correct syntax. Perhaps a form by name is not the default member of Forms collection - I never bothered to figure that one out either.

[CJ_London]

have not thought about why ! is the correct (only?) method when it comes to certain recordset references such as when referring to a recordset field by name

I think you will find that by definition the fields are latebound - the recordset is created during execution and is effectively a collection. Same for forms!myform - myform is only added to the forms collection when opened. Otherwise your code would fail compilation unless the referenced form was open at that time - clearly not feasible for an entire app - all forms referenced by code would need to be open.

However the properties and methods of the collection (be it recordset, forms, controls etc are made available when the object is defined. In vba if you enter 'forms.' then the intellisense will show the properties and methods available to the forms collection.

[Micron]

I think you will find that by definition the fields are latebound

That seems logical.