What is BM_CLICK & button id in senddlgitemmessage in VBA

looks like homework...

Visual Basic Language Specification -- 2.2.1 Type Characters
http://msdn.microsoft.com/library/en-us/vbls7/html/vblrfVBSpec2_2_1.asp

x = &H8000
y = &H8000& 'Produces a different value

The trailing ampersand tells VB it's a Long value (4 byte)

#1 BM_Click
the user in that program is defining a message handler and the bm_click is the name of the message with the id being the hex number you see after it.  its a constant and the code out from it is its value expressed as hex

#2 its in the code there is no table of them because they are programmer assigned

In windows users can define custom messages they can also override or intercept standard windows messages.

#3 you cant find all button id's he created the id's programmers assign ids to their resources although modern compilers do this for you you can also by hand create the resource file and assign id's and custom message handlers to those id's (that old school though)
ok addendum to 3  you can just get a resource editor and open the executable and you will see all of the id's and names etc.

#4
All windows messages have the same parameters.. and that is what you are seeing..

looks like homework...

Visual Basic Language Specification -- 2.2.1 Type Characters
http://msdn.microsoft.com/library/en-us/vbls7/html/vblrfVBSpec2_2_1.asp

x = &H8000
y = &H8000& 'Produces a different value

The trailing ampersand tells VB it's a Long value (4 byte)

#1 BM_Click
the user in that program is defining a message handler and the bm_click is the name of the message with the id being the hex number you see after it.  its a constant and the code out from it is its value expressed as hex

#2 its in the code there is no table of them because they are programmer assigned

In windows users can define custom messages they can also override or intercept standard windows messages.

#3 you cant find all button id's he created the id's programmers assign ids to their resources although modern compilers do this for you you can also by hand create the resource file and assign id's and custom message handlers to those id's (that old school though)
ok addendum to 3  you can just get a resource editor and open the executable and you will see all of the id's and names etc.

#4
All windows messages have the same parameters.. and that is what you are seeing..

looks like homework...

Visual Basic Language Specification -- 2.2.1 Type Characters
http://msdn.microsoft.com/library/en-us/vbls7/html/vblrfVBSpec2_2_1.asp

x = &H8000
y = &H8000& 'Produces a different value

The trailing ampersand tells VB it's a Long value (4 byte)

#1 BM_Click
the user in that program is defining a message handler and the bm_click is the name of the message with the id being the hex number you see after it.  its a constant and the code out from it is its value expressed as hex

#2 its in the code there is no table of them because they are programmer assigned

In windows users can define custom messages they can also override or intercept standard windows messages.

#3 you cant find all button id's he created the id's programmers assign ids to their resources although modern compilers do this for you you can also by hand create the resource file and assign id's and custom message handlers to those id's (that old school though)
ok addendum to 3  you can just get a resource editor and open the executable and you will see all of the id's and names etc.

#4
All windows messages have the same parameters.. and that is what you are seeing..

looks like homework...

Visual Basic Language Specification -- 2.2.1 Type Characters
http://msdn.microsoft.com/library/en-us/vbls7/html/vblrfVBSpec2_2_1.asp

x = &H8000
y = &H8000& 'Produces a different value

The trailing ampersand tells VB it's a Long value (4 byte)

#1 BM_Click
the user in that program is defining a message handler and the bm_click is the name of the message with the id being the hex number you see after it.  its a constant and the code out from it is its value expressed as hex

#2 its in the code there is no table of them because they are programmer assigned

In windows users can define custom messages they can also override or intercept standard windows messages.

#3 you cant find all button id's he created the id's programmers assign ids to their resources although modern compilers do this for you you can also by hand create the resource file and assign id's and custom message handlers to those id's (that old school though)
ok addendum to 3  you can just get a resource editor and open the executable and you will see all of the id's and names etc.

#4
All windows messages have the same parameters.. and that is what you are seeing..

looks like homework...

Visual Basic Language Specification -- 2.2.1 Type Characters
http://msdn.microsoft.com/library/en-us/vbls7/html/vblrfVBSpec2_2_1.asp

x = &H8000
y = &H8000& 'Produces a different value

The trailing ampersand tells VB it's a Long value (4 byte)

#1 BM_Click
the user in that program is defining a message handler and the bm_click is the name of the message with the id being the hex number you see after it.  its a constant and the code out from it is its value expressed as hex

#2 its in the code there is no table of them because they are programmer assigned

In windows users can define custom messages they can also override or intercept standard windows messages.

#3 you cant find all button id's he created the id's programmers assign ids to their resources although modern compilers do this for you you can also by hand create the resource file and assign id's and custom message handlers to those id's (that old school though)
ok addendum to 3  you can just get a resource editor and open the executable and you will see all of the id's and names etc.

#4
All windows messages have the same parameters.. and that is what you are seeing..