Well, that's certainly the preferred solution. You must always take care when saving your forms to ensure that:
-- The right notbook page is selected
-- Colors are properly setup (if doing dynamic highlighting)
-- Filters have been removed
-- the proper index has been selected in Order/Range
-- etc.
I use a script to verify that things are where I want them; I run it just before creating a distribution to send out to a client.
As far as your ealier questions are concerned:
A step by step might be a bit difficult, as I'm not completely clear on your form's design, but the key points are:
1. It's a good idea to manually name anything you intend to call in code. To do that,
select the object in question, inspect (right-click), choose Properties, and then enter a new name.
2. Ctrl+Space is a shortcut for displaying the Object Inspector at design time. Make sure you're displaying both tabs; that lets you navigate the objects on your form more easily.
3. Remember that the Notebook itself is a different object than the pages it contains. Each page is also a separate object. I generally use the object view to select the notbook and then right click it to get to the Propety sheet.
4. Using a number as part of the name is a preference. I generally use descriptive names, though there are times when a trailing number can be useful, especially if you're using code to control various things. In that case, it can make your code more generic.
Hope this helps...
-- Lance
