Hi Woody,
the procedure name indicates that your controlname is
SheetsWebsComboBox
not
Sheets_Webs
look at the procedure declaration line -->
Private Sub SheetsWebsComboBox_AfterUpdate()
control Name --> SheetsWebsComboBox
event --> AfterUpdate
procedure name --> SheetsWebsComboBox_AfterUpdate
Type --> Sub (instead of Function)
scope --> Private to the form -- may not be used by external processes
why are you putting ProductSpecification in front of the controlname?
You do something like that in a query because a query can have more than
one source... a form can have just one recordset --
Is ProductSpecification a form? If so, you need
Forms!ProductSpecification.Sheets_Webs_controlname
.... but if you are in the code behind your form, you can just refer to
the form as "Me"
--> Me.Sheets_Webs_controlname
where
Sheets_Webs_controlname
is the Name property of the control for sheets/webs.
'~~~~~~~~~~~~~~~~~~~~
PROPERTIES AND METHODS
Just like in the real world, every object has properties and methods.
Properties are like adjectives that describe an object
Methods are like verbs and define actions an object can do
For instance, you are a human and have properties such as hair color,
eye color, height, weight, ... and methods such as eat, walk, run, jump,
.... make babies -- Add to a collection
If you become familiar with the different types of objects that Access
can use and the properties that define them and the methods they can do
(and what triggers them), you will be on your way!
In the design view, you can show the property sheet, which will show
information for the selected item(s).
~~~~ turn on Properties window ~~~~
When you are in the design view, turn on/off the Properties window -->
1. from menu: View, Properties
OR
2. right-click and choose Properties from the shortcut menu
and then click on various objects. The properties window changes as you
change what is selected. If you have multiple objects selected, the
values for the properties they have in common will be displayed
Try it!
~~~~ Name property ~~~~
Procedures are NAMED according to the object name (except the form
object), so ALWAYS change the NAME property of any object to something
logical. For example, if you have a command button named cmdClose, its
event procedure may be something like this:
Private Sub cmdClose _Click()
If Me.Dirty Then Me.Dirty = False
DoCmd.Close acForm, Me.Name, acSaveNo
End Sub
When the properties window is displayed and only one thing is selected,
the Name appears in the title bar of the Properties window
If multiple items are selected, you will see "Multiple Selection" on the
title bar.
~~~~ ControlSource, SourceObject ~~~~
It is important to realize that the Name is NOT what is displayed in a
control. If the control is (for instance a textbox or combo box), you
will see the ControlSource displayed.
If the object is (for instance) a subform or subreport, what you see
displayed is the SourceObject
For bound objects, I like to make the Name property match the source
property (this does not, by the way, follow naming conventions, but for
me, it eases confusion)
As always, avoid using spaces and special characters when naming objects
-- use the underscore character _ to separate and use mixed case for
readability
~~~~ FieldList ~~~~
To see what fields are available so they can be placed on a form or
report: from the menu, choose View, Field List. This is a toggle – as
is the Field List icon on the toolbar (the icon is a rectangle
containing writing with a blue title bar on top).
When you drag a field from the field list to a form or report, the field
name becomes the ControlSource and the field description becomes the
status bar text. Change the name property to something logical to you
before continuing.
Warm Regards,
Crystal
*
have an awesome day
*
MVP Access
Remote Programming and Training
strive4peace2006 at yahoo.com
*
