Abstract: A data profiling module receives user selection of spreadsheets, and the data from the selected spreadsheets is profiled. At least one matching column is identified among the spreadsheets selected. The data profiling module calculates a match metric for the at least one matching column, and unifies the spreadsheets into a single composite spreadsheet using the at least one identified matching column. A preview view of a composite spreadsheet is generated, visually indicating the at least one matching column, any non-matching columns between the spreadsheets, and the match metric for the matching columns. An action history module identifies spreadsheets for use in the procedure, and stores any action applied to the spreadsheets as a procedure template that can be applied to a plurality of other spreadsheets.

Abstract: A data profiling module receives user selection of spreadsheets, and the data from the selected spreadsheets is profiled. At least one matching column is identified among the spreadsheets selected. The data profiling module calculates a match metric for the at least one matching column, and unifies the spreadsheets into a single composite spreadsheet using the at least one identified matching column. A preview view of a composite spreadsheet is generated, visually indicating the at least one matching column, any non-matching columns between the spreadsheets, and the match metric for the matching columns. An action history module identifies spreadsheets for use in the procedure, and stores any action applied to the spreadsheets as a procedure template that can be applied to a plurality of other spreadsheets.

Abstract: The present invention provides the capability to use customized procedures to manipulate and control objects in graphic implementations. It provides externalizes much of the underlying object manipulation functionality. A customized procedure is executed at various "trigger" points including: the expiration of a specified period of time; the opening or closing of a window; or, when input from a mouse input device is received. There are several different types of mouse events: mouse button down; mouse move with button down; mouse move with no button down; and mouse button up. A graphic object associated with a customized procedure that is triggered by a mouse event is called a "button object." The customized procedure associated with a button object has four parameters: buttonobj, hitobj, win, and eventinfo. The buttonobj parameter refers to the graphic object having a button procedure that is currently being executed.