VBA declaration order of "Attribute VB_Control"s keeps changing

[PMBottas]

Hi,
Does anyone know why would the declaration order of the Attribute VB_Control... statements would change.
I'm not deleting or adding any controls but it seems every time that I click one or more of them , the declaration order in the module changes.
This happens in any and all worksheet modules.

For example this:

Attribute VB_Name = "WS__Schedule"
Attribute VB_Base = "0{00020820-0000-0000-C000-000000000046}"
Attribute VB_GlobalNameSpace = False
Attribute VB_Creatable = False
Attribute VB_PredeclaredId = True
Attribute VB_Exposed = True
Attribute VB_TemplateDerived = False
Attribute VB_Customizable = True
Attribute VB_Control = "bttnDeleteScheduleEntry, 13, 0, MSForms, CommandButton2"
Attribute VB_Control = "bttnAddScheduleEntry, 12, 1, MSForms, CommandButton2"
Attribute VB_Control = "bttnCalculateShortages, 10, 2, MSForms, CommandButton2"
Attribute VB_Control = "spinAdjustPriority, 6, 3, MSForms, SpinButton2"
Attribute VB_Control = "bttnModifyScheduleEntry, 15, 4, MSForms, CommandButton2"
[\code]

becomes this
[code]
Attribute VB_Name = "WS__Schedule"
Attribute VB_Base = "0{00020820-0000-0000-C000-000000000046}"
Attribute VB_GlobalNameSpace = False
Attribute VB_Creatable = False
Attribute VB_PredeclaredId = True
Attribute VB_Exposed = True
Attribute VB_TemplateDerived = False
Attribute VB_Customizable = True
Attribute VB_Control = "spinAdjustPriority, 6, 0, MSForms, SpinButton2"
Attribute VB_Control = "bttnCalculateShortages, 10, 1, MSForms, CommandButton2"
Attribute VB_Control = "bttnAddScheduleEntry, 12, 2, MSForms, CommandButton2"
Attribute VB_Control = "bttnDeleteScheduleEntry, 13, 3, MSForms, CommandButton2"
Attribute VB_Control = "bttnModifyScheduleEntry, 15, 4, MSForms, CommandButton2"
'---------------------------------------------------------------------------------------
[\code]


Now, this may seem like a small thing, a non-starter even, except that I have the workbook under source code control. So, when I go and 'diff' the working copy, it show a change in a module that I'm 99.99999% sure that I made no changes in, yet it forces me to go look.

Any ideas what the underlying cause is and is there anyway to stop it?

Thanks in advance
Paul

 

[ww4612]

i don't know how it happens. maybe you can try this solution.

dim a as string, b as string, c as string
a="xxx"
b="yyy"
c="zzz"
Attribute VB_1=a
Attribute VB_2=b
Attribute VB_3=c

 

[PMBottas]

ww4612 : Thanks for the suggestion, but it doesn't work.

As you have it, it generates an error as the code is outside a procedure (as the Attribute statement is in the module header and you can't have Dims and Assignment statements there), so I tried this:

Private Const attribBttnModifyScheduleEntry as String = "bttnModifyScheduleEntry, 15, 0, MSForms, CommandButton2"
Attribute VB_Control = attribBttnModifyScheduleEntry

but that throws a runtime error #32809...which I believe indicates that the workbook is corrupt...

but thanks again!

Does anyone else have any input on this?
Paul

Afterthought... hmmm... maybe add the controls dynamically at workbook open? I assume that this can be done, correct?

 

[HenneyB]

Did you ever find anything out with this? I have a similar problem, but instead of just being rearranged it deletes the attributes for my command buttons and combobox