You can also produce a complete rendering of all the meta-data information in a table into a simple XML instance which you can then process and use on other programming environments as you see fit. This is used to import the data into the SQL or ORACLE or other database styles by some deployments. This form (bulk XML) is useful if you want to export all the meta-data of a database into a common and simple XML format for import to another tool. This is NOT the same as a proper XML schema, which the other export screen (see link above) supports.
The basic process of using this dialog is the following four steps.
A) Select the type of output you wish to create (ASN source or XML meta data).
B) Select what table you wish to output from.
C) Set any options such as the default module names.
The check box Match Registry ID has no use at present. It was formerly used to match up the record number used in the central registry with those used in the access tables and your data concepts.
The check box Append ASN.1 stubs is used to control the inclusion of any named ASN stubs to the module level build. If selected, it will seek for well named ASN text files to include in the build. If they are found they will be included. If they are not found, the position in the source file where they would be included will have a comment. The files will be the name of each FADD with "stubs" append, as in: IMstubs.txt Such files can be useful when developing ASN where portions of the code are included from outside sources rather than in the database.
The check box Append XML stubs is used in a similar fashion to control the XML import process, but is now overcome by the controls present in the Export XML dialog.
Select Format
Select the type of output which you seek to create, either an 
Select Tables
A collection of check boxes to select the set of tables which will be used in the output process. The default setting represents the tables that would normally be output by an SDO check of a standard. 
XML Import Source
A primitive means to specify the relative path of the schema set, used in naming the schemas import table to point to each other. Now overcome the controls present in the 
XML Stub Folders
A primitive means to specify the relative path of where the schema set will be written to the user PC. Now overcome the controls present in the Export XML Dialog.
Output File
The name of the file to be output by the routines. 
View Result button
When pressed, whatever viewer the user has registered for this file type (ASN or XSD) is fired off to view the result of the run. 
Cancel button
A close button for this dialog.
Do It button
The go button for this dialog. When pressed, the selected tables will be output in the selected way, producing the named file(s). 
Namespace to use
The ASN 
Draft Text Name
The name to be appended to the Descriptive name or the XML name, if the appending checkboxes are checked. 
Append Draft_ to XML Tag
Appends the word draft_ to the XML type name field value so that record entries can be easily grouped or told apart from other values. Used with the registry data to test drive a set of new records. 
Append Draft_ to Descriptive Name
Appends the word draft_ to the Descriptive name field value so that record entries can be easily grouped or told apart from other values. Often used with the registry data to test drive a set of new records being uploaded.