ERROR "91" Object Variable or with block variable not set

The little block of code below is giving me fits. It generates an error 91, and I have tried a large number of solutions but I am stumped. I feel pretty sure that I am not handling object variable assignments properly but don't know how to fix it. Any help would be appreciated. The degger indicates that the error occurs on the "with .controls ("textbox1")" line but I don't see VBD ever being set to a value so I think that is where the problem starts.

Sub Change_Userform()

Dim VBP As VBIDE.VBProject
Dim VBC As VBIDE.VBComponent
Dim VBD As UserForm


Set VBP = ThisWorkbook.VBProject
Set VBC = VBP.VBComponents("Calc") 'this is my userform name
Set VBD = VBC.Designer

with VBD
with .controls("textBox1")
.value = "12345"
end with
end with


End Sub

A userform is displayed when the routine first runs that displays about 30 parameters in text boxes that the user can edit/tweak/tune. When they are satisfied with the values (they don't actually have to change them they can use the defaults) they run the routine which predicts bandwidth use for different types of facilities. The parameters are the result of study by various groups and are changed rarely and then reused by a larger group who run the code for project planning. On the form there is a "save" button that they can use if they change a parameter as the new default. The sub routine is in the main code module and is called when the "save" button is pushed (a toggle button).

No you can't save them. It appears that the intent was to allow user to input data into a userform so it could be saved in a spreadsheet, more like a data entry GUI than anything else. The values for the controls are set at "design time", and facilities are provided to add forms and controls during "run time". But once the control has a value it can't be changed directly. Here is a link that demostrrates the code: http://www.xtremevbtalk.com/archive/.../t-317970.html

The comment I think you are referring to is: " I had the subs in userform itself (and assigned them to actions such as Userform_Click) NOT in a separate module. They're working beautifully now.". It doesn't say you can't run the code "from" the form, it says you can't have the code "in" the form. I have it in an external module that is called by the form when the "save" button is pushed.

Josie - Thank you, thank you, thank you. That is the answer. External to the form the code works perfectly. This makes things just a bit more complicated (i need to create a flag that the "save" button was pushed, save the data in the form, query the flag and write to the values after the form exits if the user wants the new parameters saved). But my original goal is now achievable. I will have to admit that I am a bit puzzled by the designers intent in coding the language this way. But it won't be the last time I have that question!