Question about using library items in forms

Question

After a long time I am again returning to this perpetual fountain of Dreamweaver knowledge.
I am converting a site from AGL to DW. In AGL I used a separate template for the forms (there are over 10) and used "components" to create the different forms. Each form shared features with other forms but were not identical, all together 5 components. When I converted over to DW the 5 compnents were made into 5 "library items" but neither the form template or the library items work, by that I mean they do not update if I make a change.
Hence I want to make 5 new library items to use in the forms my question is this: when I choose an item to put in the form like a text field or radio button I always get this window.
Though I read the documentation I am still not really clear about the "style" option so I just choose "no label tag." What is this used for? Any examples of how it is used?
Regarding "position" before or after the item, what is this all about? I have been choosing "after form item" but I don't really know what the difference is and what advantages or disadvantages acrue from these choices.
Regarding "Access key" and "Tab index" I sort of have the idea of what it is about but an example of how they work in action would clear up any nebulosity.
But my real puzzle is with the following which pops up at the end when I am inserting a form items.
Since the library items are not separate forms in themselves I have NOT added the form tag because my reasoning is that when I make the new form templates it will have the requisite form tags. Am I correct in this line of thinking? Or do I have to add form tags every time I add form elements to a form? I really don't want to have to do the whole thing over again if I get it wrong. So if one of you kind souls could guide me in doing it right the first time I would really appreciate it.
I am using a MBP, OS X 10.6.8, DW CS6
BvL

Answer 1

To declare constants create a Package-Specification in a pll and deifne all your constants there, something like:
PACKAGE PK_CONSTANTS IS
  RC_SUCCESS CONSTANT PLS_INTEGER := 1;
  RC_FAILURE CONSTANT PLS_INTEGER := 0;
  RC_YEAR_DATA_NOT_FOUND := 50;
END;Then attach that pll to all your forms-modules, and use it like
IF rc = PK_CONSTANTS.RC_YEAR_DATA_NOT_FOUND THEN
END IF;A word about exceptions or errors: In my eyes its clearer (and in case of exceptions even better) to raise an exception than to hide it behind return-codes.