|Publication number||US6631497 B1|
|Application number||US 09/356,606|
|Publication date||Oct 7, 2003|
|Filing date||Jul 19, 1999|
|Priority date||Jul 19, 1999|
|Also published as||CA2379855A1, CA2379855C, EP1212704A1, EP1212704A4, WO2001006418A1|
|Publication number||09356606, 356606, US 6631497 B1, US 6631497B1, US-B1-6631497, US6631497 B1, US6631497B1|
|Inventors||Ardeshir Jamshidi, Farzad Farahod, Hardeep Singh|
|Original Assignee||International Business Machines Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (13), Referenced by (165), Classifications (10), Legal Events (12)|
|External Links: USPTO, USPTO Assignment, Espacenet|
Portions of this patent application contain materials that are subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
Spreadsheet programs are commonly used for mathematical and database applications such as record-keeping, “what-if” and optimization analysis, calculations, charting and graphical analysis. Electronic spreadsheets offer many advantages over their paper counterparts. For one, electronic spreadsheets allow users to manipulate more information than their paper counterparts.
Also, spreadsheet programs allow users to.perform “what if” scenarios so that, after a set of mathematical relationships has been entered into a worksheet, the spreadsheet can be recalculated using different sets of assumptions, with the results of each recalculation appearing dynamically. Performing this operation manually, with paper and pencil, would require recalculating every relationship in the model with each change made. Thus, electronic spreadsheets offer dramatic improvements in ease of creating, editing, and using mathematical models over traditional financial modeling tools such as the accountant's columnar pad, pencil, and calculator.
Although electronic spreadsheets are capable of manipulating vast amounts of data, there is no convenient system for placing data in the spreadsheets. Spreadsheets have cells containing specific sets of rules and instructions defined by the end user for the manipulation and presentation of data. While defining such sets of rules and instructions for each cell is an easy task, the task of directing and transferring distributed data to each cell can be quite complex.
A conventional way of doing this imports a set of desired data from a database into the spreadsheet by reading a file of the database that is stored with the data and importing it to the spreadsheet. Another conventional method includes a step of retrieving necessary data from a database to input the data into a table. For this retrieval, a programmed retrieval formula is required for the database. The former conventional method, in which a file of database is directly read, requires that the constitution of the database be understood, as well as the format of the file stored with data, and the like. The format of any table to be read is thus restricted by the storing format of the database, constituting a difficulty in a selective reading of data.
In most cases, the format of the data to be extracted from a database does not have a sufficient adaptability to the table format of an employed spreadsheet, thus requiring the user to re-form the table format of read data into an adaptive one. The latter method, in which a retrieval formula is input for database retrieval, also needs the constitution of the database to be understood, in addition to the necessary preparation of a retrieval formula by the user, who is thus required to master both how to write the formula for database retrieval and how to use a given spreadsheet.
Typically, to bind a relational database management system (RDBMS) data source to a particular cell in a spreadsheet, specific macros and coding need to be done. Writing the macros and code requires a user to have knowledge of programming in Visual Basic, Excel objects methods and properties, and Structured Query Language (SQL). Additionally, the code has to be adjusted or revamped every time the database is updated or business logic evolves. Furthermore this code is specific to one particular spreadsheet application.
In sum, a user must be familiar with details of the constitution of the database to effectively utilize data therefrom on a spreadsheet. Such a requirement puts a large burden on the user to make an effective use of the database on a spreadsheet, thus constituting a hindrance to using the spreadsheet to analyze the content of the database.
The invention binds data from a data source to one or more cells in a spreadsheet by importing a data object and defining a data source model for the data object; associating the data object with the one or more cells in the spreadsheet; and binding data from the data object to the one or more cells upon request.
Implementations of the invention include one more of the following. The importing and associating steps are performed during design time, and the binding step is performed during run time. The imported data is stored in an Extended Markup Language (XML) format. The imported object is stored in a tree. The associating step includes dragging-and-dropping one or more children of the data object into one or more cells in the spreadsheet. The data source can be a database, in which case SQL code is generated during run-time. If the data source is a business object, a method or a function associated with the data source can be invoked.
Advantages of the invention include one or more of the following. The invention provides a “seamless” two-way link between the spreadsheet and an external data source such as a RDBMS, so that the two appear to be fully integrated. In such a seamless integration, the transfer of data to and from the external data source would appear to be completely automatic, occurring in the normal course of the spreadsheet's recalculation. The invention provides a user-friendly interface with a drag-and-drop paradigm that provides the spreadsheet end user with the ability to view the entire distributed environment. Users can then simply drag-and-drop their desired distributed data source(s) to each cell of the spreadsheet. The invention thus seamlessly propagates and reflects the changes made to each cell to underlying binding data source(s) in a platform independent manner.
Moreover, distributed (or otherwise) data source(s) in a computing environment can be viewed. Such data sources can be defined or modeled into one or more data source schema(s) by simple dragging-and-dropping of entities representing data source(s). This requires no programming or technical knowledge of such concepts as SQL, or other data-source (including database) technologies on behalf of the spreadsheet user. Thus, the invention encapsulates and hides the coding and programming that would otherwise be required for the spreadsheet cell-data source binding to take place.
Other features and advantages will become apparent from the following description, including the drawings and the claims.
FIG. 1 is a diagram illustrating a system for automatically binding a cell in a spreadsheet with one or more data sources.
FIG. 2A is a flowchart of a process associated with a model controller.
FIG. 2B is a flowchart of a process associated with a virtual object controller.
FIG. 2C is a flowchart of a process associated with a link manager.
FIG. 3 is an exemplary user interface for the model controller and the virtual object controller.
FIG. 4 is an exemplary user interface for the link manager.
FIG. 5 is a flowchart of a process for binding data sources to cells.
FIG. 6 is a schematic diagram of a computer for supporting automatic cell binding.
FIG. 1 shows a system 100 for providing automatic spreadsheet cell-data source binding. The system includes a run-time manager 102 and a design-time manager 104. The design-time manager 104 communicates with a repository 106, which in turn communicates with a data source engine 108. The data source engine 108 communicates with various database sources 110 as well as non-database sources of data, including business objects 120. The database sources 110 can be JDBC 112, OLED 114, or ODBC 116, for example. Further, the data sources are not simply database objects but can be non-database objects such as DLLs 122, COM objects 124, Java objects 126, and executables, among others. The data source engine 108 also communicates with the run-time manager 102 to provide the cell-data source binding upon user request.
The design-time manager 104 has a data modeler, which is a user-friendly graphical user interface (GUI) control that exposes all existing data sources (RDBMS or otherwise) in a distributed (or otherwise) computing environment. For example, RDBMS data sources include databases and all objects that are encapsulated by the database. These include tables, columns within each table, and stored procedures, among others. Examples of non-RDBMS data source include a DLL or a Java package, among others. All objects that are encapsulated by such data sources are also exposed to the users. These can include public methods, functions, parameters, etc. Users can then examine each object and set certain properties of such objects. Furthermore users can create new schema(s) and include different objects from different data sources into such schema(s) by a simple drag-and-drop user interface. The modeler handles the creation of all such schema(s). During design-time, a user can drag-and-drop specific data source(s) as displayed in the modeler to individual cells of the spreadsheet. A binding manager in the design-time manager 104 then handles all binding processes, regardless of the type of data source selected.
In the system of FIG. 1, data sources in the distributed computing environment are viewed using a model viewer component. The user then creates a model and imports certain data sources from the distributed environment into the model. This is done by a simple drag-and-drop operation of selecting the desired data sources and then dragging them into the model. The system of FIG. 1 will note the read/write attribute of each data source imported. This will be used later to provide a bi-directional capability of transmitting data between the cell and the data source.
The user then creates one or more views to the model. Views are referred to as virtual objects. These views are created using a virtual object controller (see FIG. 2B). The user can then simply drag and drop elements of a data source to create the views to the corresponding model. Furthermore, a user can define the parameter(s) of each element of, a view via a special GUI wizard. Thus, for example, the value passed to a particular parameter of a Java method is defined by stating the name of the cell, or by a formula that is based on some values. In this manner, data sources can be mixed into one model and each data source can bind to an individual cell. The mixing of data sources into one model and making the distinction at bind time provides modeling capability in addition to the binding capability.
The user then binds the elements of a model view to individual cells on the spreadsheet using a link manager (see FIG. 2C), which displays all models and their respective views in a tree structure control. The binding is done by a simple drag-and-drop operation, including dragging an element of a view (e.g. a column, or a Java method) and dropping it on a specific individual cell on an Excel worksheet.
The run-time manager 102 will then oversee the transformation, conversion and transition of data from and to a data source to its binding cell, and vice versa. Operations performed by the run-time manager 102 include: opening a connection from the data source to the cell (and vice versa), constructing and executing specific SQL statements (if the underlying binding data source is RDBMS), or invoking specific methods and functions (if the underlying binding data source is non-RDBMS such as a DLL or a Java package, etc.); and conversion, transformation and transition of data between each cell and its underlying binding data source.
All metadata information with regard to binding is serialized within the worksheet as an Extensible Markup Language (XML) object. XML is a subset of the ISO Standard Generalized Markup Language (SGML), which is a standard document formatting language that enables a publisher to create a single document source that can be viewed, displayed, or printed in a variety of ways. SGML is a large, complex formatting language that is not especially suited to the Web. HTML and XML are simplified versions of SGML that are specifically designed to support Web pages. XML is very similar to HTML (and is in fact interoperable with HTML), but it does not rely on a single DTD. Instead, XML provides a standard mechanism for any document builder to define new XML tags within any XML document. In addition to being a markup language, XML is a meta-language that can define new DTDs. An XML DTD specifies the format for a particular XML document type, identifying what tags could or should appear within the document. A document can contain or point to its DTD; therefore, XML is a self-describing data format. An XML document does not need to be defined by a DTD. But if a DTD does exist, it is used to validate that a document matches a specific format. Any XML parser can dynamically parse the embedded DTD to learn how to parse the XML tags within the document and to validate the contents of the document.
In the system of FIG. 1, the runtime environment seamlessly reads all such metadata information and according the binding instructions transfers data between the cell and the underlying bound data source. Such instructions include SQL code that need to be executed (if the underlying bound data source is a database object), or the location of the method, and function that needs to be executed (if the underlying bound data source is a non-database object). Thus, the system of FIG. 1 models the data source information and the document template into an XML format and then binds them together inside the spreadsheet. At runtime this meta data is used to locate the data source over the network, to fetch and update data into and from the spreadsheet.
FIGS. 2A, 2B and 2C show processes 200, 250 and 300 associated with a model controller, a virtual object controller, and a link manager, respectively. The controllers are part of one GUI control that has been divided into three windows or panels, embodiments of which are shown in FIGS. 3 and 4 and discussed below. The model controller allows the user to create a model and import data sources to that model. Once imported, the model is displayed in a tree with the top level node being the name of the model. The virtual object controller allows users to drag and drop individual elements of a model from the model controller into a view. Again, everything is displayed in a tree with the top level model being the name of the view that the user creates.
The link manager allows models and all their associated views to be displayed in a tree structure with the top level being the model with its child nodes being the views. As a view to a particular model is created in the middle window, a node is added to the link manager tree accordingly under the model. Users can select, and drag and drop an element of a view from the Link Manager tree into an individual cell on the spread sheet. As this is done, the link path gets displayed on the right panel side of the link manager window. The link path is the full path describing the name of worksheet.cell.datasource path to which the data source being dragged and dropped is bound.
Shown in FIG. 2A is the model controller which is used for importing data sources into a user defined model. This component stores all necessary meta data information such as the URL location and path of each data source, their read/write attributes, and parameters.
In process 200, meta data information regarding parameter definition, origin and location of all elements brought into a particular view are stored as XML. The term parameter here refers not only to the parameters of methods and functions but also to the arguments appearing in the WHERE clause part of a SQL statement defining a particular view that may contain database related objects. For example, a user may bring in column 1 from table t1, and column 2 from table t2 into the view. The SQL that will be generated will select t1.c1, t2.c2 from t1,t2 where t1.c1=<whatever>, t2.c2=<whatever>. The <whatever> portions are noted by a GUI wizard (that is part of this component), and the user can enter them in the wizard. The <whatever> clause can be arbitrarily defined-as actual values or as a complicated formula or even the name of a particular cell in the worksheet (e.g. select t1.c1, t2.c2 from t1,t2 where t1.c1=cell1=75 and t2.c2=cell2*cell1+45). The SQL statements are automatically generated, and a user friendly wizard assists the user to define the WHERE clauses of the generated SQL statement, thus freeing the user from having to know SQL in depth.
Data source models are defined by importing objects using the data source engine 108 (step 202). As discussed earlier, the data sources are not simply database objects but can be non-database objects such as Java objects, COM objects, DLLs, and executables. Next, the models are stored in the data source repository 106 as XML objects (step 204). Finally, the imported objects are displayed in a tree (step 206). The tree stores information on each object, along with the object's children. Thus, data stored by the tree can include tables, columns, and Java objects and their associated methods, among others.
To illustrate, an exemplary model can have eleven data sources. They may include three tables, and two stored procedures imported from a database, two Java objects each having three methods, and a DLL having four functions. User can drag and drop two of the columns from one table, 3 columns from another table, 2 of the methods from the first Java object, and a method from the second Java object, and one function from the DLL into a view.
FIG. 2B shows a process 250 associated with a virtual object controller. The virtual object controller allows the user to define one or more views into a specific data source model. The process 250 involves defining a specific view name and then dragging-and-dropping individual elements of a model (e.g. table columns, Java methods, COM methods, stored procedures, functions, among others) into that view. First, in step 252, the user defines various virtual objects based on the data source models defined in step 202 of FIG. 2A. For database objects, step 254 includes invoking a SQL query builder wizard which generates the SQL code. The wizard allows the user to seamlessly integrate each cell as part of the SQL query definitional criteria. Alternatively, if the data source is not a database, the wizard takes into consideration parameter(s) of the underlying non-database data source (step 256). For non-database virtual objects, the definition of each virtual object involves the drag-and-drop of the object into the cell. For instance, the parameter may include the method of a Java object. Finally, the virtual objects are stored and displayed in a tree structure (step 258).
Referring now to FIG. 2C, a process 300 associated with a link manager is shown. The link manager displays all models along with all the views that are defined for that model in a tree structure control (step 302). Users can then drag and drop an element of a view to a particular cell on the worksheet. The system in turn stores the necessary meta data information with a worksheet of the spreadsheet. The meta data information includes the necessary SQL statement for passing the data between the cell and the underlying data source (if it is a database object), or the location and the parameters that need to be set in order to invoke a method or function if the underlying data source is non-database information. The wizard responsible for handling the parameter assignment can also be invoked at this stage as well in order to overwrite the default parameter value as defined by the virtual object controller.
FIGS. 3 and 4 show exemplary user interfaces for the model controller, the virtual object controller, and the link manager discussed above. These controllers are seamlessly integrated with an exemplary spreadsheet, which in this case is Microsoft Corp.'s Excel spreadsheet. The controllers are coded in Visual Basic Application and are embedded within Excel.
Turning first to FIG. 3, a spreadsheet 350 is shown. Documents in the spreadsheet can be viewed as having two main components: a template and data that populates such templates. Document templates simply provide the manner in which data is to be manipulated and subsequently presented to an end user. Data is an entity that originates from one or more network based distributed (or otherwise) sources. In the spreadsheet, each cell is viewed as an independent GUI control object tied to one or more data source object(s). Each such cell will maintain its own specific behavior as defined by its contained characteristics as defined by the spreadsheet user. Because each cell is viewed and manipulated as a GUI control, a collection of such cells will establish an independent entity capable of navigating through one or more distributed data source(s).
The system presents one GUI control that has been divided into three windows or panels, embodiments of which are shown in FIGS. 3 and 4. The model controller allows the user to create a model and import data sources to that model in a model view 362. Table relationships associated with the imported data sources are shown in the table view 364. Once imported, the model is displayed in a tree with the top level node being the name of the model. The virtual object controller allows users to drag and drop individual elements of a model from the model controller into an object view 366. Again, everything is displayed in a tree with the top level model being the name the view user creates. In the example of FIG. 3, meta data associated with the source object is shown. As the source object is a database, the meta data includes a source 368, a column name 372 and a column type 374.
FIG. 4 shows an exemplary link manager user interface. The link manager allows models and all their associated views to be displayed in a tree structure 382 with the top level being the model with its child nodes being the views. As a view to a particular model is created in the middle window 384, a node is added to the link manager tree accordingly under the model. Users can select, and drag and drop an element of a view from the link manager tree into an individual cell on the spread sheet. As this is done, the link path gets displayed on the window 386 of the link manager window. The link path is the full path describing the name of worksheet.cell.datasource path to which the data source being dragged and dropped is bound.
A process 400 associated with the run-time environment is shown in FIG. 5. First, the spreadsheet worksheet is read and all binding information is extracted (step 402). Where the data source is a database, the binding information extracted from the worksheet includes:
1. Link Path Info (e.g. cellname.tableName.columnName)
2. The full path location of the data source (e.g. directory and/or URL location of the database)
3. Connection information (e.g. connection string)
4. SQL associated with the binding (e.g Update, Insert, Delete, Select)
5. Parameters associated with the SQL (e.g. in the statement: select column1 from table1 where column1=cell1*25, the parameter is considered to be column1 and its value is considered to be cell1*25 which is computed at runtime prior to actually executing the SQL statement.)
6. Max rows for fetching purposes
Where the data source is a non-database, the binding information extracted from the worksheet includes:
1. Type of the data source (e.g. COM, DLL, EJB, CORBA, etc.)
2. Based on the type of data source specific information is stored (e.g. for COM objects, their Interface identifications are stored).
3. Link Path Info (e.g. cellname.objectname.methodname)
4. A list of parameters to the data source and how they are computed. This includes the type of the parameter whether it is input only or output only or input/output, in addition to how it is to be evaluated).
The runtime environment knows the type of data source the cell is bound to and processes the binding information accordingly. The run-time environment interacts with the binding cell and the data source using SQL code (step 404). The SQL code generation is done through a user friendly GUI wizard. The wizard will provide different types of SQL statements that can be generated by the wizard including Select, Insert, Update and Delete. The interactive process is as follows:
1. Wizard loads up the model information (e.g., tables, views, stored procedures, among others)
2. User selects a specific object displayed to him from the list. This includes for example a table along with its columns.
3. These selected objects will be included in the type of SQL statement to be generated.
4. User will then enter parameter criteria information (e.g. the terms that will go into the WHERE clause. This is done via selecting columns names from a list.)
5. Wizard displays the generated SQL to the user for possible manual adjustments; and,
6. Virtual object (in this case a virtual table) is created based on the generated SQL statement:
If the data source is not a database, such as a COM object, the process 400 will seamlessly, for example, create a CoCreateInstance in order to instantiate the COM object and then, by knowing the name of the method that was serialized within the worksheet for that particular cell, the process 400 invokes the appropriate method using COM (APIs). Similarly, if the data source is a Corba object or a Java Bean method, the process 400 would call the appropriate interface and mechanism in order to invoke the binding method.
The invention may be implemented in digital hardware or computer software, or a combination of both. Preferably, the invention is implemented in a computer program executed in a computer system. Such a computer system may include a processor, a data storage system, at least one input device, and an output device. FIG. 6 illustrates one such computer system 600, including a processor (CPU) 610, a RAM 620, a ROM 622 and an I/O controller 630 coupled by a CPU bus 650. The I/O controller 630 is also coupled by an I/O bus 650 to input devices such as a keyboard 660, a mouse 670, and output devices such as a monitor 680. Additionally, one or more data storage devices 692 is connected to the I/O bus via an I/O interface 690.
Further, variations to the basic computer system of FIG. 6 are within the scope of the present invention. For example, instead of using a mouse as user input devices, a pressure-sensitive pen, digitizer or tablet may be used to generate the drawn segment location information. The user input is thus sampled to define the segment.
The above described software can be implemented in a high level procedural or object-oriented programming language to operate on a dedicated or embedded system. However, the programs can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language.
Each such computer program can be stored on a storage medium or device (e.g., CD-ROM, hard disk or magnetic diskette) that is readable by a general or special purpose programmable computer for configuring and operating the computer when the storage medium or device is read by the computer to perform the procedures described. The system also may be implemented as a computer-readable storage medium, configured with a computer program, where the storage medium so configured causes a computer to operate in a specific and predefined manner.
While the invention has been shown and described with reference to an embodiment thereof, those skilled in the art will understand that the above and other changes in form and detail may be made without departing from the spirit and scope of the following claims.
Other embodiments are within the scope of the following claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5657460 *||Apr 11, 1995||Aug 12, 1997||Data View, Inc.||System and method for storing and displaying data|
|US5734889||Jan 18, 1996||Mar 31, 1998||Nec Corporation||Method and apparatus for retrieving data and inputting retrieved data to spreadsheet including descriptive sentence input means and natural language interface means|
|US5752253 *||Jun 28, 1995||May 12, 1998||Bull, S.A.||Process and device for the automatic generation of spreadsheets|
|US5819293||Jun 6, 1996||Oct 6, 1998||Microsoft Corporation||Automatic Spreadsheet forms|
|US5842018 *||Jun 6, 1995||Nov 24, 1998||Microsoft Corporation||Method and system for referring to and binding to objects using identifier objects|
|US5883623||Apr 21, 1997||Mar 16, 1999||Borland International, Inc.||System and methods for building spreadsheet applications|
|US5893123||Jun 22, 1995||Apr 6, 1999||Tuinenga; Paul W.||System and method of integrating a spreadsheet and external program having output data calculated automatically in response to input data from the spreadsheet|
|US5897649 *||Nov 25, 1997||Apr 27, 1999||Peoplesoft, Inc||Interactive formula processing system for SQL databases|
|US5953716 *||May 30, 1996||Sep 14, 1999||Massachusetts Inst Technology||Querying heterogeneous data sources distributed over a network using context interchange|
|US5970476 *||Sep 19, 1996||Oct 19, 1999||Manufacturing Management Systems, Inc.||Method and apparatus for industrial data acquisition and product costing|
|US6002865 *||Apr 20, 1995||Dec 14, 1999||Thomsen; Erik C.||Location structure for a multi-dimensional spreadsheet|
|US6275866 *||Mar 3, 1998||Aug 14, 2001||Mathsoft Engineering & Education, Inc.||Manipulation and coupling of object oriented components|
|US6292811 *||Jul 13, 1998||Sep 18, 2001||Modernsoft, Inc.||Populating cells of an electronic financial statement|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6850956||Sep 8, 2000||Feb 1, 2005||Corel Inc.||Method and apparatus for obtaining and storing data during automated data processing|
|US6859907||Aug 9, 1999||Feb 22, 2005||Cognex Technology And Investment Corporation||Large data set storage and display for electronic spreadsheets applied to machine vision|
|US6868193||Sep 8, 2000||Mar 15, 2005||Corel Inc.||Method and apparatus for varying automated data processing|
|US6925593||Sep 8, 2000||Aug 2, 2005||Corel Corporation||Method and apparatus for transferring data during automated data processing|
|US6938030||Sep 8, 2000||Aug 30, 2005||Corel Corporation||Method and apparatus for facilitating accurate automated processing of data|
|US6944865 *||Sep 8, 2000||Sep 13, 2005||Corel Corporation||Method and apparatus for saving a definition for automated data processing|
|US6961922||Sep 8, 2000||Nov 1, 2005||Corel Corporation||Method and apparatus for defining operations to be performed during automated data processing|
|US6988241 *||Nov 15, 2000||Jan 17, 2006||International Business Machines Corporation||Client side, web-based spreadsheet|
|US6990632 *||Feb 28, 2003||Jan 24, 2006||Microsoft Corporation||Method and system for inferring a schema from a hierarchical data structure for use in a spreadsheet|
|US7000223||Sep 8, 2000||Feb 14, 2006||Corel Corporation||Method and apparatus for preparing a definition to control automated data processing|
|US7003722 *||Feb 28, 2003||Feb 21, 2006||Microsoft Corporation||Method and system for converting a schema-based hierarchical data structure into a flat data structure|
|US7017112 *||Feb 28, 2003||Mar 21, 2006||Microsoft Corporation||Importing and exporting markup language data in a spreadsheet application document|
|US7069499||Sep 16, 2002||Jun 27, 2006||Cognex Technology And Investment Company||Spreadsheet having a clocked delay line object, for processing a continuous data stream|
|US7096422 *||Feb 28, 2003||Aug 22, 2006||Microsoft Corporation||Markup language visual mapping|
|US7117430 *||Feb 27, 2001||Oct 3, 2006||Microsoft Corporation||Spreadsheet error checker|
|US7143340 *||Jun 27, 2003||Nov 28, 2006||Microsoft Corporation||Row sharing techniques for grid controls|
|US7146422 *||May 1, 2000||Dec 5, 2006||Intel Corporation||Method and apparatus for validating documents based on a validation template|
|US7155665 *||Jun 18, 2001||Dec 26, 2006||Microsoft Corporation||Method for creating an embedded database in a spreadsheet|
|US7155666 *||Nov 1, 2001||Dec 26, 2006||Sun Microsystems, Inc.||Creating and displaying document undo configuration using nested test modes|
|US7155667 *||Jun 21, 2000||Dec 26, 2006||Microsoft Corporation||User interface for integrated spreadsheets and word processing tables|
|US7185279 *||Dec 15, 2000||Feb 27, 2007||Master Mine Software, Inc.||Data mining and reporting|
|US7197696 *||Jun 5, 2003||Mar 27, 2007||Pavan Vidyadhar Muzumdar||System, method and computer program product to populate data into spreadsheets and execute functions and programs within the same|
|US7249316 *||Jan 9, 2006||Jul 24, 2007||Microsoft Corporation||Importing and exporting markup language data in a spreadsheet application document|
|US7251776 *||Jul 11, 2002||Jul 31, 2007||Netview Technologies, Inc.||System and method for efficiently and flexibly utilizing spreadsheet information|
|US7266763 *||Nov 26, 2002||Sep 4, 2007||Microsoft Corporation||User defined spreadsheet functions|
|US7296219||Nov 15, 2000||Nov 13, 2007||International Business Machines Corporation||Client side, web-based calculator|
|US7296238||Sep 8, 2000||Nov 13, 2007||Corel Corporation||Method and apparatus for triggering automated processing of data|
|US7299223||Jul 15, 2004||Nov 20, 2007||Oracle International Corporation||Spreadsheet to SQL translation|
|US7350141 *||Sep 16, 2004||Mar 25, 2008||Microsoft Corporation||User interface for integrated spreadsheets and word processing tables|
|US7376895 *||Nov 8, 2002||May 20, 2008||Wuxi Evermore Software, Inc.||Data object oriented repository system|
|US7379943 *||Jan 28, 2005||May 27, 2008||Microsoft Corporation||Method and system for bidirectionally data binding a control of a template|
|US7395497 *||Oct 31, 2003||Jul 1, 2008||Emc Corporation||System and methods for processing large datasets|
|US7412645 *||May 4, 2004||Aug 12, 2008||Microsoft Corporation||User interface for integrated spreadsheets and word processing tables|
|US7415481 *||Sep 30, 2004||Aug 19, 2008||Microsoft Corporation||Method and implementation for referencing of dynamic data within spreadsheet formulas|
|US7421646 *||Jan 3, 2007||Sep 2, 2008||Microsoft Corporation||System and method for schemaless data mapping|
|US7426688||Nov 2, 2004||Sep 16, 2008||Hewlett-Packard Development Company, L.P.||Embedded spreadsheet commands|
|US7467148 *||Dec 8, 2004||Dec 16, 2008||Microsoft Corporation||Reporting status of external references in a spreadsheet without updating|
|US7472339 *||Jun 22, 2001||Dec 30, 2008||International Business Machines Corporation||Method in an electronic spreadsheet for persistently self-replicating multiple ranges of cells through a copy-paste operation and a self-replication table|
|US7506243 *||Oct 9, 2004||Mar 17, 2009||Microsoft Corporation||System and method for integrating spreadsheets and word processing tables|
|US7512897 *||Oct 19, 2005||Mar 31, 2009||Microsoft Corporation||Integrated method for creating a refreshable web query|
|US7523390 *||Oct 8, 2004||Apr 21, 2009||Microsoft Corporation||Spreadsheet fields in text|
|US7539944 *||Feb 18, 2005||May 26, 2009||Microsoft Corporation||Importing data from a source document into a destination document|
|US7549115 *||Oct 8, 2004||Jun 16, 2009||Microsoft Corporation||System and method for integrated spreadsheets and word processing tables|
|US7640493||Jan 23, 2006||Dec 29, 2009||Microsoft Corporation||Importing and exporting markup language data in a spreadsheet application document|
|US7657830 *||May 4, 2005||Feb 2, 2010||Microsoft Corporation||Layout size sharing in a grid layout for a user interface|
|US7664804||Jun 1, 2004||Feb 16, 2010||Microsoft Corporation||Method, system, and apparatus for exposing workbook ranges as data sources|
|US7673227 *||Sep 16, 2004||Mar 2, 2010||Microsoft Corporation||User interface for integrated spreadsheets and word processing tables|
|US7676843||Jun 24, 2004||Mar 9, 2010||Microsoft Corporation||Executing applications at appropriate trust levels|
|US7685152 *||Jan 10, 2006||Mar 23, 2010||International Business Machines Corporation||Method and apparatus for loading data from a spreadsheet to a relational database table|
|US7689929||Feb 11, 2005||Mar 30, 2010||Microsoft Corporation||Methods and systems of providing information to computer users|
|US7692636||Sep 30, 2004||Apr 6, 2010||Microsoft Corporation||Systems and methods for handwriting to a screen|
|US7693860 *||Mar 18, 2005||Apr 6, 2010||Microsoft Corporation||Method and system to associate cell and item metadata|
|US7698287 *||Sep 30, 2004||Apr 13, 2010||Microsoft Corporation||Design of spreadsheet functions for working with tables of data|
|US7702997||Oct 8, 2004||Apr 20, 2010||Microsoft Corporation||Spreadsheet fields in text|
|US7703007 *||Dec 27, 2005||Apr 20, 2010||Microsoft Corporation||Importing and exporting markup language data in a spreadsheet application document|
|US7712022||Nov 15, 2004||May 4, 2010||Microsoft Corporation||Mutually exclusive options in electronic forms|
|US7712048||Jul 23, 2004||May 4, 2010||Microsoft Corporation||Task-sensitive methods and systems for displaying command sets|
|US7720842||Jul 16, 2001||May 18, 2010||Informatica Corporation||Value-chained queries in analytic applications|
|US7721190||Nov 16, 2004||May 18, 2010||Microsoft Corporation||Methods and systems for server side form processing|
|US7725834||Mar 4, 2005||May 25, 2010||Microsoft Corporation||Designer-created aspect for an electronic form template|
|US7743063||Jan 27, 2005||Jun 22, 2010||Microsoft Corporation||Methods and systems for delivering software via a network|
|US7747657||Jun 8, 2007||Jun 29, 2010||International Business Machines Corporation||Mapping hierarchical data from a query result into a tabular format with jagged rows|
|US7747673||Sep 8, 2000||Jun 29, 2010||Corel Corporation||Method and apparatus for communicating during automated data processing|
|US7747939 *||May 31, 2005||Jun 29, 2010||Microsoft Corporation||Generating free form reports within a data array|
|US7774620||May 27, 2004||Aug 10, 2010||Microsoft Corporation||Executing applications at appropriate trust levels|
|US7779027||Sep 13, 2004||Aug 17, 2010||Microsoft Corporation||Methods, systems, architectures and data structures for delivering software via a network|
|US7779343||Jan 30, 2006||Aug 17, 2010||Microsoft Corporation||Opening network-enabled electronic documents|
|US7792847||Nov 7, 2005||Sep 7, 2010||Microsoft Corporation||Converting structured reports to formulas|
|US7797621 *||Oct 26, 2006||Sep 14, 2010||Bank Of America Corporation||Method and system for altering data during navigation between data cells|
|US7805433||Oct 14, 2005||Sep 28, 2010||Microsoft Corporation||Multidimensional cube functions|
|US7818677||Aug 12, 2004||Oct 19, 2010||Microsoft Corporation||Single window navigation methods and systems|
|US7849108 *||Mar 13, 2008||Dec 7, 2010||Fundriver, Inc.||Methods and systems for establishing a database|
|US7853833||Sep 8, 2000||Dec 14, 2010||Corel Corporation||Method and apparatus for enhancing reliability of automated data processing|
|US7865477||Oct 15, 2007||Jan 4, 2011||Microsoft Corporation||System and method for real-time validation of structured data files|
|US7882426||Aug 9, 1999||Feb 1, 2011||Cognex Corporation||Conditional cell execution in electronic spreadsheets|
|US7900134||Nov 8, 2006||Mar 1, 2011||Microsoft Corporation||Authoring arbitrary XML documents using DHTML and XSLT|
|US7904801||Dec 15, 2004||Mar 8, 2011||Microsoft Corporation||Recursive sections in electronic forms|
|US7913159||Mar 28, 2003||Mar 22, 2011||Microsoft Corporation||System and method for real-time validation of structured data files|
|US7925621||Jan 29, 2008||Apr 12, 2011||Microsoft Corporation||Installing a solution|
|US7926027 *||Oct 19, 2004||Apr 12, 2011||Microsoft Corporation||Binding to business objects and web services|
|US7930626||Oct 31, 2003||Apr 19, 2011||Hewlett-Packard Development Company L.P.||Determining a location for placing data in a spreadsheet based on a location of the data source|
|US7937651||Jan 14, 2005||May 3, 2011||Microsoft Corporation||Structural editing operations for network forms|
|US7945850||Feb 27, 2007||May 17, 2011||Mastermine Software, Inc.||Data mining and reporting|
|US7949953||May 28, 2004||May 24, 2011||Sap Aktiengesellschaft||Designing and generating charts to graphically represent data in a data source|
|US7953767||Oct 5, 2004||May 31, 2011||Sap Ag||Developing applications using configurable patterns|
|US7954046||Dec 9, 2005||May 31, 2011||Microsoft Corporation||Importing and exporting markup language data in a spreadsheet application document|
|US7962618||May 19, 2010||Jun 14, 2011||Corel Corporation||Method and apparatus for communicating during automated data processing|
|US7991804||Jul 30, 2004||Aug 2, 2011||Microsoft Corporation||Method, system, and apparatus for exposing workbooks as data sources|
|US8001459||Dec 5, 2005||Aug 16, 2011||Microsoft Corporation||Enabling electronic documents for limited-capability computing devices|
|US8015481 *||Feb 14, 2005||Sep 6, 2011||Xapio Gmbh||Method for generating source code in a procedural, re-entrant-compatible programming language using a spreadsheet representation|
|US8046732||Dec 30, 2005||Oct 25, 2011||Sap Ag||Distribution of data changes in pattern configurations|
|US8051373 *||Jan 6, 2006||Nov 1, 2011||Microsoft Corporation||Method and system for converting a schema-based hierarchical data structure into a flat data structure|
|US8073879||Mar 25, 2004||Dec 6, 2011||Microsoft Corporation||Systems and methods that transform constructs from domain to domain|
|US8086959 *||Jan 6, 2006||Dec 27, 2011||Microsoft Corporation||Method and system for inferring a schema from a hierarchical data structure for use in a spreadsheet|
|US8095565 *||May 5, 2006||Jan 10, 2012||Microsoft Corporation||Metadata driven user interface|
|US8126937 *||Oct 5, 2004||Feb 28, 2012||Sap Ag||Visual database modeling|
|US8195701 *||Apr 8, 2009||Jun 5, 2012||Ithaka Harbors, Inc.||Integration of data sets into documents for interactive exploration|
|US8234293||Sep 8, 2005||Jul 31, 2012||Microsoft Corporation||Autocompleting with queries to a database|
|US8250461||Aug 21, 2012||International Business Machines Corporation||Persistently self-replicating multiple ranges of cells through a table|
|US8255792 *||Apr 20, 2007||Aug 28, 2012||Cisco Technology, Inc.||Techniques for binding scalable vector graphics to associated information|
|US8271369 *||Mar 12, 2004||Sep 18, 2012||Norman Gilmore||Financial modeling and forecasting system|
|US8271576||May 19, 2010||Sep 18, 2012||Corel Corporation||Method and apparatus for communicating during automated data processing|
|US8306999 *||Mar 24, 2008||Nov 6, 2012||Sas Institute Inc.||Computer-implemented systems, methods, and computer program product for providing row-level security in a database network|
|US8341512||Oct 31, 2007||Dec 25, 2012||Microsoft Corporation||Method for capturing design-time and run-time formulas associated with a cell|
|US8429518||May 13, 2011||Apr 23, 2013||Mastermine Software, Inc.||Data mining and reporting|
|US8442996 *||Apr 12, 2006||May 14, 2013||Enrico Maim||Methods for granting access to resources modifiable by users in a computer environment, and resources structured therefore|
|US8538913 *||Sep 7, 2011||Sep 17, 2013||American Express Travel Related Services Company, Inc.||Test strategy system and method for accounts held direct at-fund|
|US8578399||Jul 30, 2004||Nov 5, 2013||Microsoft Corporation||Method, system, and apparatus for providing access to workbook models through remote function cells|
|US8584003 *||Jan 3, 2007||Nov 12, 2013||Yiu-Ming Leung||System and method for schemaless data mapping with nested tables|
|US8601361 *||Aug 6, 2007||Dec 3, 2013||Apple Inc.||Automatically populating and/or generating tables using data extracted from files|
|US8612852 *||Sep 30, 2003||Dec 17, 2013||Oracle International Corporation||Omniportlet-declaratively publish data in a portal without code|
|US8694601||May 12, 2011||Apr 8, 2014||8324450 Canada Inc.||Method and apparatus for communicating during automated data processing|
|US8732656||Feb 24, 2012||May 20, 2014||International Business Machines Corporation||Development environment for managing database aware software projects|
|US8739116||Feb 24, 2012||May 27, 2014||International Business Machines Corporation||Development environment configured to generate application source code from database objects|
|US8793706||Dec 16, 2010||Jul 29, 2014||Microsoft Corporation||Metadata-based eventing supporting operations on data|
|US8838627 *||May 30, 2006||Sep 16, 2014||Sap Ag||Systems and methods for providing template based output management|
|US8862646 *||Mar 25, 2014||Oct 14, 2014||PlusAmp, Inc.||Data file discovery, visualization, and importing|
|US8862773||Dec 5, 2012||Oct 14, 2014||Intel Corporation||Scalable network apparatus for content based switching or validation acceleration|
|US8972437||Dec 23, 2009||Mar 3, 2015||Apple Inc.||Auto-population of a table|
|US9053083||Nov 4, 2011||Jun 9, 2015||Microsoft Technology Licensing, Llc||Interaction between web gadgets and spreadsheets|
|US9058370 *||Feb 27, 2007||Jun 16, 2015||International Business Machines Corporation||Method, system and program product for defining imports into and exports out from a database system using spread sheets by use of a control language|
|US9076015||May 13, 2013||Jul 7, 2015||Enrico Maim||Methods for granting access to resources modifiable by users in a computer environment, and resources structured therefore|
|US20020013786 *||Dec 15, 2000||Jan 31, 2002||Robert Machalek||Data mining and reporting|
|US20020055948 *||Nov 1, 2001||May 9, 2002||Sun Microsystems, Inc||Method and apparatus for handling a plurality of test modes for a computer generated document|
|US20020055953 *||Nov 2, 2001||May 9, 2002||Falko Tesch||Method and apparatus for handling scenarios in spreadsheet documents|
|US20040103366 *||Nov 26, 2002||May 27, 2004||Microsoft Corporation||User defined spreadsheet functions|
|US20040119727 *||Dec 19, 2002||Jun 24, 2004||International Business Machines Corporation||Extracting displayed numerical data from displayed documents received from communication networks, e.g. World Wide Web, and processing the extracted numerical data independent of the received document|
|US20040172590 *||Feb 28, 2003||Sep 2, 2004||Microsoft Corporation||Method and system for converting a schema-based hierarchical data structure into a flat data structure|
|US20040172591 *||Feb 28, 2003||Sep 2, 2004||Microsoft Corporation||Method and system for inferring a schema from a hierarchical data structure for use in a spreadsheet|
|US20040172592 *||Feb 28, 2003||Sep 2, 2004||Microsoft Corporation||Importing and exporting markup language data in a spreadsheet application document|
|US20040172616 *||Feb 28, 2003||Sep 2, 2004||Microsoft Corporation||Markup language visual mapping|
|US20040181378 *||Mar 12, 2004||Sep 16, 2004||Norman Gilmore||Financial modeling and forecasting system|
|US20040252136 *||May 28, 2004||Dec 16, 2004||Ankur Bhatt||Designing and generating charts to graphically represent data in a data source|
|US20040255239 *||Oct 31, 2003||Dec 16, 2004||Ankur Bhatt||Generating electronic reports of data displayed in a computer user interface list view|
|US20040268226 *||Jun 26, 2003||Dec 30, 2004||International Business Machines Corporation, Armonk, New York||Facilitating the development of computer programs|
|US20040268227 *||Jun 27, 2003||Dec 30, 2004||Brid Regis L.F.||Row sharing techniques for grid controls|
|US20040268303 *||Jun 7, 2004||Dec 30, 2004||Mari Abe||System, method, and computer program product for generating a web application with dynamic content|
|US20050044496 *||Oct 8, 2004||Feb 24, 2005||Microsoft Corporation||Spreadsheet fields in text|
|US20050055634 *||Sep 30, 2003||Mar 10, 2005||Oracle International Corporation||Omniportlet-declaratively publish data in a portal without code|
|US20050102212 *||Nov 7, 2003||May 12, 2005||Qd Financial, Llc||Systems and methods for generating audited and unaudited financial statements and reports|
|US20050108623 *||Dec 8, 2004||May 19, 2005||Microsoft Corporation||Reporting status of external references in a spreadsheet without updating|
|US20050177573 *||Feb 18, 2005||Aug 11, 2005||Microsoft Corporation||Integrated method for creating a refreshable web query|
|US20050188352 *||Feb 14, 2005||Aug 25, 2005||Bruno Jager||Method for generating source code in a procedural, re-entrant-compatible programming language using a spreadsheet representation|
|US20050216508 *||Mar 25, 2004||Sep 29, 2005||Maria Meijer Henricus J||Systems and methods that transform constructs from domain to domain|
|US20050267853 *||Jun 1, 2004||Dec 1, 2005||Microsoft Corporation||Method, system, and apparatus for exposing workbook ranges as data sources|
|US20060010118 *||Jul 11, 2005||Jan 12, 2006||Juergen Sattler||System and method for role-based spreadsheet data integration|
|US20060010367 *||Jul 11, 2005||Jan 12, 2006||Juergen Sattler||System and method for spreadsheet data integration|
|US20070143149 *||Oct 31, 2006||Jun 21, 2007||Buttner Mark D||Data tagging and report customization method and apparatus|
|US20070198918 *||Apr 20, 2007||Aug 23, 2007||Yishay Mor||Techniques for binding scalable vector graphics to associated information|
|US20080016440 *||Jul 14, 2006||Jan 17, 2008||Microsoft Corporation||Programming And Managing Sensor Networks|
|US20090089653 *||Sep 28, 2007||Apr 2, 2009||Microsoft Corporation||Auto-generation and syndication of tables as forms|
|US20090327213 *||Jun 25, 2008||Dec 31, 2009||Microsoft Corporation||Document index for handheld application navigation|
|US20090327240 *||Aug 20, 2008||Dec 31, 2009||Meehan Stephen W||System And Method For Organizing Data In A Dynamic User-Customizable Interface For Search And Display|
|US20110106795 *||Apr 12, 2006||May 5, 2011||Enrico Maim||Methods for granting access to resources modifiable by users in a computer environment, and resources structured therefore|
|US20110161796 *||Dec 31, 2009||Jun 30, 2011||Edward Charles Laikin||FormDB: a process to create a forms database in Excel without user programming|
|US20110191665 *||Aug 12, 2010||Aug 4, 2011||Robert Handsaker||System and method for dynamic data access in a spreadsheet with external parameters|
|US20120011154 *||Jan 12, 2012||American Express Travel Related Services Company, Inc.||Test strategy system and method for accounts held direct at-fund|
|US20120110428 *||May 3, 2012||Microsoft Corporation||Spreadsheet model for distributed computations|
|US20130013994 *||Jan 10, 2013||Robert Handsaker||System and method for dynamic data access in a spreadsheet with external parameters|
|CN101322096B||Dec 5, 2006||Oct 10, 2012||微软公司||Metadata driven user interface|
|CN102508839A *||Sep 22, 2011||Jun 20, 2012||用友软件股份有限公司||Data processing device and data processing method|
|EP1569135A1||Jan 19, 2004||Aug 31, 2005||Sap Ag||A database management system and a method of managing a database|
|EP1605367A2 *||May 31, 2005||Dec 14, 2005||Microsoft Corporation||Method,system, and apparatus for making available workbook ranges as data sources|
|EP1622045A2 *||May 25, 2005||Feb 1, 2006||Microsoft Corporation||Method, system, and apparatus for exposing workbooks as data sources|
|WO2005045725A2 *||Oct 21, 2004||May 19, 2005||Hewlett Packard Development Co||Determining a location for placing data in a spreadsheet based on a location of the data source|
|U.S. Classification||715/205, 707/E17.006|
|International Classification||G06F17/30, G06F12/00, G06Q10/00, G06F17/24|
|Cooperative Classification||G06F17/246, G06F17/30569|
|European Classification||G06F17/30S5V, G06F17/24S|
|Mar 28, 2001||AS||Assignment|
Owner name: INFORMIX SOFTWARE, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JAMSHIDI, ARDESHIR;FARAHOD, FARZAD;SINGH, HARDEEP;REEL/FRAME:011661/0976;SIGNING DATES FROM 20010213 TO 20010312
|Feb 1, 2002||AS||Assignment|
|Jul 6, 2004||CC||Certificate of correction|
|Apr 26, 2005||AS||Assignment|
|Jun 14, 2005||AS||Assignment|
|Jan 10, 2007||FPAY||Fee payment|
Year of fee payment: 4
|Jun 8, 2007||AS||Assignment|
Owner name: WELLS FARGO FOOTHILL, INC., MASSACHUSETTS
Free format text: SECURITY AGREEMENT;ASSIGNOR:MAINSTAR SOFTWARE CORPORATION;REEL/FRAME:019399/0427
Effective date: 20070518
|Aug 10, 2007||AS||Assignment|
Owner name: WELLS FARGO FOOTHILL, INC., MASSACHUSETTS
Free format text: CORRECTION TO REEL/FRAME 019399/0427;ASSIGNOR:ROCKET SOFTWARE, INC.;REEL/FRAME:019679/0322
Effective date: 20070518
|Aug 23, 2010||AS||Assignment|
Owner name: WELLS FARGO FOOTHILL, INC., MASSACHUSETTS
Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE THE EXISTENCE OF THE SECURITY AGREEMENT (EVEN AS CORRECTED BY REEL 019679, FRAME 0322) PREVIOUSLY RECORDED ON REEL 019399 FRAME 0427. ASSIGNOR(S) HEREBY CONFIRMS THE THAT NEITHER AN ASSIGNMENT TO ROCKET SOFTWARE, INC. NOR FROM ROCKET SOFTWARE, INC. TO WELLS FARGO FOOTHILL, INC. EVER OCCURRED;ASSIGNOR:ROCKET SOFTWARE, INC.;REEL/FRAME:024864/0759
Effective date: 20070608
Owner name: WELLS FARGO FOOTHILL, INC., MASSACHUSETTS
Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE THE EXISTENCE OF THE SECURITY AGREEMENT PREVIOUSLY RECORDED ON REEL 016686 FRAME 0300. ASSIGNOR(S) HEREBY CONFIRMS THE THAT NEITHER AN ASSIGNMENT TO ROCKET SOFTWARE, INC. NOR FROM ROCKET SOFTWARE, INC. TO WELLS FARGO FOOTHILL, INC. EVER OCCURRED;ASSIGNOR:ROCKET SOFTWARE, INC.;REEL/FRAME:024864/0756
Effective date: 20050614
|Jan 29, 2011||FPAY||Fee payment|
Year of fee payment: 8
|Jun 3, 2011||AS||Assignment|
Owner name: WELLS FARGO FOOTHILL, INC., MASSACHUSETTS
Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE EXISTENCE OF A SECURITY AGREEMENT PREVIOUSLY RECORDED ON REEL016172 FRAME 0026. ASSIGNOR(S) HEREBY CONFIRMS THE THAT NEITHER AN ASSIGNMENT TO ROCKET SOFTWARE, INC. NOR FROM ROCKET SOFTWARE, INC. TO WELLS FARGO FOOTHILL, INC. EVER OCCURRED.;ASSIGNOR:ROCKET SOFTWARE, INC.;REEL/FRAME:026390/0366
Effective date: 20050426
|Jan 21, 2015||FPAY||Fee payment|
Year of fee payment: 12