Try OpenEdge Now
skip to main content
.NET Open Clients
Passing Parameters : ABL temp-table to ADO.NET DataTable mappings
 

ABL temp-table to ADO.NET DataTable mappings

The ABL temp-table maps closely to an ADO.NET DataTable. The temp-table can be passed in a remote ABL procedure or user-defined function, between .NET and the AppServer, as a parameter or as part of a ProDataSet parameter (see ABL temp-table to ADO.NET DataTable mappings). For static temp-table parameters, ProxyGen creates extended ADO.NET DataTable classes for each unique temp-table definition. For dynamic temp-tables, ProxyGen uses the standard ADO.NET DataTable class for the parameters.
In ABL, you can define a temp-table as being LIKE a database table, and you can add fields of any type to this definition, or you can define the table as a set of fields independent of any particular database table. You can also define indexes to manage large sets of data efficiently.
An ADO.NET DataTable shares all of these characteristics. Thus, OpenEdge supports:
*The creation of a temp-table on the AppServer
*Passing that temp-table to a .NET client application
*Allowing that application to manipulate the data using an ADO.NET DataTable
*Returning data changes to the AppServer to update any data source for the temp-table
To support the mapping of ABL temp-tables to ADO.NET DataTables, OpenEdge establishes detailed correspondences between temp-table components and similar ADO.NET objects. This includes the mapping of such elements as temp-table field data types and temp-table component attributes. For more information on the mapping of temp-table field data types, see Passing TABLE and TABLE-HANDLE parameters. The following sections describe the mapping of temp-table components and their attributes:
*Mapping temp-table components
*Mapping temp-table component attributes
*Resolving differences between ABL and .NET date and time implementations
*Mapping the XML-NODE-TYPE attribute to ADO.NET
* Mapping temp-table components
* Mapping temp-table component attributes
* Resolving differences between ABL and .NET date and time implementations
* Mapping the XML-NODE-TYPE attribute to ADO.NET