Quote:
Originally Posted by macropod
Your autonew macro populates your userform's combobox with the reference to 'Complaints Adjudicator'. Nothing else that I can see changes what the combobox is populated with, so I can't see where the second code snippet in your first post comes into play - it's not even in the document code. You have four options for ComboBox3:
"Financial Ombudsman Service",
"Financial Services Ombudsman's Bureau",
"Pensions Ombudsman"
'Else'
Since there's nothing in the Combobox3 code for your Complaints Support team,
the 'Else' kicks in and you get 'Complaints Adjudicator'.
|
This is the master document, when I need ComboBox2 to state "Complaints Support" I amend .ComboBox2.Value = "Complaints Adjudicator" to .ComboBox2.Value = "Complaints Support".
Unless I'm missing something I feel the issue is likely to be with the module rather than the form coding, my reason for this is because when the form is launched ComboBox2 always states "Complaints Adjudicator" even if I remove "Complaints Adjudicator" from the module completely. The form code relates to when the Combo Boxes are changed, which come into play once the form has been launched.
Quote:
Originally Posted by fumei
BoringDavid, why do you have the additems in Module1. I would put it in the UserInitialize event.
|
I picked up the project after the person before left without finishing it, I ended up getting it because I am young and know what a mouse is... So everything is self-taught and a lot of what I am doing is based on my former colleagues work!
I hadn't thought of adding them to the UserInitialize Event (mainly because I haven't heard of a UserInitialize Event).
12-12-2013, 02:32 AM
Similar Threads
Combo Box
Windows XP 
Office 2010 32bit
Threaded Mode