Stored procedure type tree structure

The type trees generated by the Database Interface Designer for stored procedures used for outputs from a map are slightly different from the ones generated for tables, queries, and queries calling stored procedures (that are used as the source of data for a map).

Major differences between a type tree for a stored procedure that will be used as output and a type tree for a table that will also be used as output are:

• Whereby table and query type trees have a Column item type from which stems all of the individual column types, the type tree for a stored procedure has an Argument item type from which stems item types representing each of the arguments passed to the stored procedure.
• Instead of a Row group, the type tree for a stored procedure has a ProcedureCall type. The ProcedureCall group represents the set of arguments passed to the stored procedure for each execution of the procedure.

  The ProcedureCall group is defined in the same way as a Row type for a table or a query in the type tree. Its group format is determined by the value selected in the Row group format list in the Generate Type Tree from Tables dialog or the Generate Type Tree from Query dialog, respectively. The selected group format determines the terminator and release characters.

• Similar to the DBTable or DBSelect types in type trees for tables or queries, the type tree for a stored procedure has a DBProcedure type, which is an implied group consisting of a series of ProcedureCalls. The stored procedure is called once for each ProcedureCall in the DBProcedure output.

  For information about using stored procedures as a data target, see Using stored procedures. For information about generating type trees for a stored procedure, see From a stored procedure.