Tell me, please, that you developed your form using the special
workflow object that you downloaded from Microsoft.  You will have much
better results with it than the standard mail form as your base.

You do understand the difference between the form and the data item.  
The form is the definition of the collection of controls that display
the data items when the item is shown on the screen, as well the
controls that implement the functions you expect to see in the form,
and the interior objects which are intrinsic to the data item.  The
data item consists of all the fields that have user data in them, and,
of course, data which Outlook/Exchange uses to store and manage them.

The grand design of the Exchange/Outlook InforStore is that these two
collections are kept separate until they are mated in the screen object
that the Outlook application uses to display and functionally
manipulate the data.

You include user input in the data collection by binding user-defined
controls to user-defined fields, or by having un-bound controls and
using the click-event of the control to move the input data to a field.

Once you have your user input data moved to permanent fields in the
data item, you can then write code to move the data from those fields
to whatever external database you are using.  Or you can just keep the
data items, and use Outlook vbscript code to loop through the items,
extracting the field data that you desire in a particular operation.  
In either case, you write the code to do what you want done, and run it
from a command button click-event or other event which occurs in the
processing of data items.

Lots of fun.  Do become familiar with www.slipstick.com, as that is the
premier resource for things Exchange/Outlook.  The next best resource
is www.CDOlive.com.

Hollis D. Paul [MVP - Outlook]
Hollis@outlookbythesound.com
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2195
http://search.support.microsoft.com/kb/c.asp?FR=0&SD=TECH&LN=EN-US
     
Mukilteo, WA  USA