Abstract: Metadata is used to create customized user interface (UI) portions for an application. The metadata may be XML-based and can be interpreted and then rendered to implement a customized UI that also supports data binding between data and the UI controls. Once created, the metadata is processed by a rendering engine to display the UI controls. An interpreter may be used to interpret the metadata file before it is sent to the rendering engine. Neither the rendering engine nor the interpreter needs knowledge of the host application and provides support for arbitrary metadata driven UI. The metadata schema may include mechanisms to create custom controls for the UI; programmatically modify the UI controls by providing access to a code-behind assembly as well as support event handling for the UI controls.

Abstract: Data applications may be developed within an integrated development environment comprising an iterative cycle of writing source code, building the source code, running the data application, and testing the data application. The development becomes iterative because the application is torn down, redesigned, rebuilt, and re-executed if the data application is modified. Developing an application at runtime is disclosed herein, which is generally more efficient than conventional iterative techniques. As provided herein, runtime application comprising prebuilt components is presented to a user. The runtime application may be modified through modification gestures. An update assembly may be built based upon the modification gestures. The runtime application may be updated based upon the updated assembly.

Abstract: A method of tracking data through a multi-tier computing architecture includes initializing a first row pointer of a dataset with data form a database, placing changes to the data in the second row pointer of the dataset, comparing the first and second row pointers, and declaring a state of the data in response to comparing the first and second row pointers. A system for tracking data through a multi-tier architecture includes an initialize module, a change module, a compare module, and a declare module. The initialize module initializes a first row pointer of a dataset with data from a database. The change module places changes to the data in a second row pointer of the dataset. The compare module compares the first and second row pointers. The declare module declares a state of the data in response to comparing the first and second row pointers.

Abstract: A system, method, and article of manufacturer for programming processing operations within a server and more particularly to a system, method, and article of manufacturer for programming processing operations of tracking data through a multi-tier computing architecture.

Abstract: A method of tracking data through a multi-tier computing architecture includes initializing a first row pointer of a dataset with data form a database, placing changes to the data in the second row pointer of the dataset, comparing the first and second row pointers, and declaring a state of the data in response to comparing the first and second row pointers. A system for tracking data through a multi-tier architecture includes an initialize module, a change module, a compare module, and a declare module. The initialize module initializes a first row pointer of a dataset with data from a database. The change module places changes to the data in a second row pointer of the dataset. The compare module compares the first and second row pointers. The declare module declares a state of the data in response to comparing the first and second row pointers.

Abstract: A method of building a dataset in a computing system includes extracting data meeting a predetermined criteria from at least a first database, filling the dataset with data items, extracting from the first database relationships between the data items meeting the predetermined criteria, and filling the dataset with the relationships. A system for building a dataset in a computing system includes a data extraction module, a data populating module, a relationship extraction module, and a relationship populating module. The data extraction module extracts data meeting a predetermined criteria from at least a first database. The data populating module fills the dataset with data items. The relationship extraction module extracts from the first database relationships between the data items meeting the predetermined criteria. The relationship populating module fills the dataset with the relationships.

Abstract: Data is separated from source. Datasets store tables of data and a graph of the relationships between the tables. The relationship can change at any time. The relationships are described by metadata that describe primary key, foreign key, and lookups, and other relationships between tables. In one embodiment, the tables of data are typed columns of data. The dataset also includes information on the rowstate and differential preservation, therefore, the source does not need to manage states of the data access. Adapters abstract the interface to datasets. More specifically, adapters manage the input/output to the datasets of the tables of data and the relationships. Adapters can be specialized in their purpose, such as an adapter for OLE data or XML data or generalized in their purpose. Furthermore, a composite adapter is specialized for the purpose of interacting with other adapters. Adapters manage the connection to the dataset and the name of the server that hosts the dataset.

Abstract: Data is separated from source. Datasets store tables of data and a graph of the relationships between the tables. The relationship can change at any time. The relationships are described by metadata that describe primary key, foreign key, and lookups, and other relationships between tables. In one embodiment, the tables of data are typed columns of data. The dataset also includes information on the rowstate and differential preservation, therefore, the source does not need to manage states of the data access. Adapters abstract the interface to datasets. More specifically, adapters manage the input/output to the datasets of the tables of data and the relationships. Adapters can be specialized in their purpose, such as an adapter for OLE data or XML data or generalized in their purpose. Furthermore, a composite adapter is specialized for the purpose of interacting with other adapters. Adapters manage the connection to the dataset and the name of the server that hosts the dataset.