Mike, I took your general advice about using the XML parser to create custom Outlook views and repeatedly studied:
1) MSDN Library's VBA and XML examples under Outlook 2002
2) Outlook Help file examples
3) Fox Advisor's limited examples of XML and Outlook per se.
4) COM: Createobject("MSXML2.DomDocument"

... anywhere it could be Googled.
5) Etc.
Finally, after days of mental strivings (prayers) and trial and error failures, my prayers were answered and the code became manifested. This has been the sequence:
1) First, generate an appropriate custom table view manually in Outlook, modify it in Outlook to suit your special custom view needs.
2) Create an XML file generator.prg; copy the following code with Outlook OPEN, i.e.,:
#Define olFolderCalendar 9
objView = CreateView("New Calendar Table View",olFolderCalendar,0)
***
Function CreateView
Parameters strName,cnstFolderName,cnstViewType
PUBLIC objViews as Views
PUBLIC objViewCalendar as View
oOutlook = Createobject("Outlook.Application"

objXML=Createobject("MSXML2.DomDocument"
objViews = oOutlook.getnamespace("MAPI"

.GetDefaultFolder(cnstFolderName).Views
For Each objView In objViews
If objView.Name=strName
?objView.name
=STRTOFILE(objView.XML,'MyXMLfile') &&the XML suffix generates the XML code (see XML under VBA properties)
Endif
Endfor
3. Voila/hallelulia: You've just created your custom Outlook table view in XML that EVEN INCLUDES YOUR USER DEFINED FIELDS repleat with properties, format(s), etc. in XML.
Note: USER DEFINED FIELDS are practically impossible to write in XML directly. Check out what MS Outlook generated in XML for MyUserDefinedField User Defined Field:
<column>
<heading>MyUserDefinedField</heading>
<prop>
<type>boolean</type>
<width>36</width>
<style>text-align:center;padding-left:3px</style>
<format>boolicon</format>
<displayformat>3</displayformat>
</column>
4. Next, Open the (temporary) MyXMLfile itself and copy (to the clipboard) all the XML code that was generated by outlook ...via VFP's STRTOFILE(objView.XML,'MyXMLfile') statement. Open/label an XML file (notepad) of your choosing: In this example you might label that file "objViewCalendar.XML"
5. Then, make another program and copy this code into it:
#DEFINE olTableView 0
=SetTableProperties("New Calendar Table View"

&&This parameter name is arbitrary
****
FUNCTION SetTableProperties
PARAMETERS strViewName
PUBLIC objViews as Views
PUBLIC objViewCalendar as View
oOutlook = Createobject("Outlook.Application"

objXML=Createobject("MSXML2.DomDocument"
objViews = oOutlook.GetNamespace("MAPI"

.GetDefaultFolder(9).Views &&InBox
objViewCalendar = objViews.ADD(strViewName,olTableView,0)
objXML.load("objViewCalendar.XML"

objViewCalendar.XML = objXML.XML &&MUST KEEP THIS
objViewCalendar.Save
objViewCalendar.Apply
It is finished. Now just tie up any loose ends and integrate it into your COM object(s) and application.
Now that I'm 'dangerously aquainted' with XML, Microsoft.XMLDOM, Outlook's XML property, etc., I must thank you wholeheartedly for prodding me into discovering this most viable and excellent solution for programtically creating the custom Outlook view(s) in VFP.
I'm looking forward to studying your "french newsgroup" code and probing further ideas.
In the meantime I hope other users might exploit Outlook's vast potential with the above sequences.
Philip M. Traynor, DPM