KR100538547B1 - Data retrieval method and apparatus with multiple source capability - Google Patents

Abstract

The generation of an output or report on the information contained in the data source, which may be in any of two or more types of source data, is provided in a standardized or uniform manner. For example, a number of drivers are provided that are specific to different types of source data, including programming to identify structural or other characteristics of various data sources for use in defining new databases. Preferably, the new database is configured to allow a high degree of flexibility and / or rapid output or reporting, or otherwise is optimized for reporting purposes. In one embodiment, the present invention includes the conversion from one or more data sources to one or more uniform databases, preferably generating one or more key categories for organizing the data. And optionally, category groupings or rollups, and generating additional data or optional references. In one embodiment, one or more databases with uniformity of structure are created, although they may be based on two or more different data sources that may have very different structures. Different data sources are analyzed automatically, and this analysis can be used to identify and / or generate categories of data for use in organizing the information.

Description

DATA RETRIEVAL METHOD AND APPARATUS WITH MULTIPLE SOURCE CAPABILITY}

The present invention is directed to a computer-implemented system that may be in a number of different formats and that is capable of retrieving information stored in one or more of a number of different sources and providing reports and analysis based on the information. In particular, it is possible to automatically retrieve database information stored in any of a number of formats, including structural and / or relational information, without having to rely on human analysis of the source data. Computer method and apparatus.

Many ways have been developed for organizing computer-accessible information, such as relational or hierarchical database management systems, flat file data systems, spreadsheet systems, and the like. These systems are used to store, manipulate, and display countless forms of information, including accounting or other financial information, scientific or technical information, corporate or company data, name, address and phone number data, and statistical data. do. Many formats and data structures have been developed and this situation has both desirable and undesirable consequences. On the positive side, by having a variety of different types of systems, it can be optimized for different purposes (e.g., optimized for data entry or storage against the speed or flexibility of data analysis and reporting, or for corporate data). It may be possible to provide different systems that provide a user interface or other characteristic that may appeal to personal or corporate preferences. However, the growth of such information systems provides an inherent barrier in situations where it becomes useful to access information in two or more systems, for example to integrate or combine information. Examples of such situations include: (1) an accountant who wants to generate a standardized report, but each has a plurality of customers who manage the accounting data with different types of data sources; (2) a legal entity that wants to produce a uniform report, but where different departments have different legal entities or several departments using financial software; (3) a legal entity that wants to generate a uniform report but manages its accounting information in a database (or other data source) of the first type or brand, and manages its corporate information in a second type of database; (4) While studying common problems, there are groups of scientists, each of whom stores and accesses data in different types or brands of databases or other data sources. After understanding this specification, readers will understand that there are more examples. Furthermore, in some situations, even when all the desired information is stored in a single data source or a single data file, it provides a way to access the data, for example, to provide uniform and / or improved data analysis and reporting. It may be desirable to.

This situation presents difficulties for many reasons, including differences in the way information is organized and differences in the form of data sources. In some situations, even if the same database software is used, similar categories of information may be organized in different ways. For example, in the first case using the first database software package, the names of all employees of the company are stored in the first table or list, all addresses are stored in the second table or list, and all telephone numbers are 3 A user may organize a company employee's record so that a pointer or link is stored in a table or list and indicates which name is associated with which address and which phone number. However, in other instances of using the same software, each line or "record" of information may appear in a statement, with or without a link or pointer from a record in one table to a record in another table by another person organizing employee information. You can also provide a single table containing addresses and phone numbers.

In addition, different types of data sources may have different structures and / or different data storage formats or manners. For example, some database packages may be organized in a hierarchical manner (eg, tree), while others may be organized as relational databases (modeled in two-dimensional tables of rows and columns). Also, strictly as if storing data as a spreadsheet in a "flat file" format, the information may be stored in a format other than a database format. In addition, different types of data sources may store data in various formats. For example, some database products store each table, each report format, and each query as independent files in storage, such as a hard disk, while other software stores all tables, relationships, queries, reports. You can also save the format in a single file. Some products may store each record and / or field as fixed length data and / or at a fixed location in the file, while other products may store one field and the next between one record and the next, or within a record. You can also use delimiters to distinguish between fields. Even if two different software products store certain types of information in certain locations, these locations may be different for different software products. In addition, data may be encoded differently in different software products, such as using ASCII encoding in one product and multi-lingual (multi-byte) characters in another. In some cases, data may be compressed and / or encrypted.

In view of the wide variations between data types, conventionally, when trying to access stored information (eg, to standardize reports and analyzes and to combine or consolidate information from two or more databases). , Consultants or other experts analyzed each "source" data file or database individually or "manually" to understand its structure, relational data storage format, organization of data in the database, and the like. The expert will then configure some way to import or query the data in the source data file or database to achieve the desired access, integration or combination. Although this approach is feasible, it is labor-intensive because it requires human analysis, and also requires a relatively long time for an expert or consultant to complete the analytical task, sometimes requiring access, integration or combination to be performed. It is time-consuming because several days or weeks are required.

Thus, providing a system in which information in various formats or formats, or organized in various ways, can be accessed, combined, and / or integrated, thus eliminating the need for human analysis, and thus, at least partially automated, preferably For example, it would be useful to provide a less labor-intensive and less time-consuming system than the previous method.

1 is a schematic diagram showing an example of flat file data storage.

2 illustrates a directory structure in a form that can be used in connection with the data storage shown in FIG.

3A-3C illustrate examples of data storage formats that can be used in connection with the data storage shown in FIG.

4A-4F are schematic diagrams showing examples of data stored in tables in a relational database.

Fig. 5 shows a directory structure in a form that can be used in connection with the data storage shown in Figs. 4A to 4F.

Fig. 6 is a schematic diagram showing an example of flat file data storage.

7A-7D are schematic diagrams of data stored in tables in a relational database.

8 is a block diagram of a system for retrieving information according to an embodiment of the present invention.

9 is a schematic diagram of the contents of a function module according to an embodiment of the present invention.

10 is a flow diagram of a process for retrieving information in accordance with one embodiment of the present invention.

11A and 11B illustrate a pseudocode procedure for selecting or searching a directory, in accordance with an embodiment of the present invention.

Figure 12 is a schematic diagram of data stored in a table of a database 808 provided in accordance with one embodiment of the present invention.

Summary of the Invention

The present invention relates to a system for performing access to stored information, for example, to access information in two different information storage systems and to realize integration and / or combination of the information. Preferably, in one embodiment of the present invention, some or all of the relevant analyzes are performed automatically using a suitably programmed computer (without requiring human analysis). Preferably, this system is flexible because it is not inherently limited to the data format and can be configured to obtain data from virtually any computer-readable information source. Also, the system is extensible (more preferably, modularly extensible) because components may be added to allow access to additional forms, formats or organizational data. In one embodiment of the present invention, accessing, integrating or combining the data involves an enhancement of the data analysis and provides data analysis and / or reporting in a form not present or used in the original data source. Preferably, this system can be used to provide standardization of data analysis and / or reporting through several types of data sources. In one embodiment of the invention, the system is structured as well as the contents of the source data file or database to achieve the desired result (e.g., by using a text recognition, artificial intelligence and / or expert system). Also use information about. In one embodiment, the system uses this information to at least partially control how the data is made available for analysis or reporting. In one embodiment, the system uses this information to provide such analysis and reports.

The generation of an output or report on the information contained in the data source, which may be in any of two or more types of source data, is provided in a standardized or uniform manner. For example, a number of drivers are provided that are specific to different types of source data, including programming to identify structural or other characteristics of various data sources for use in defining new databases. Preferably, the new database is configured to allow a high degree of flexibility and / or rapid output or reporting, or otherwise is optimized for reporting purposes. In one embodiment, the present invention includes the conversion from one or more data sources to one or more uniform databases, preferably generating one or more key categories for organizing the data. And optionally, category groupings or rollups, and generating additional data or optional references.

In one embodiment, the present invention creates or populates a database based on accounting or other data converted from existing data files, such as data files generated by previous accounting or other software.

In one embodiment of the invention, the system creates or defines a schedule, for example, to store one or more profiles of data to be updated, and / or to automatically execute the update procedure at a predetermined time or interval. Thereby facilitating updating part or all of the new database.

In one embodiment of the present invention, an extension is provided that automatically identifies a preferred view of data, such as generating a view when one or more values are found for a given field or parameter of the data. do.

 Preferably, one or more verification or audit tools are provided to detect potential errors or problems.

Before describing the aspects of the invention, it will be useful to provide examples of various ways of storing information to facilitate understanding of the invention. This is accomplished by providing several examples, including examples of accounting information and examples of scientific or technical information. Table 1 below provides a comparison of the data types that can be stored by two different legal entities. Table 1 is intended to represent the conceptual organization of accounting or other information for two legal entities, and is not necessarily information that will be stored in the database (although it may be so if desired).

Table 1: Example of Accounting

            Corporation # 1 Corporation # 2

Account Account       Cash       Cash       Accounts Payable             Bank # 1       Accounts Receivable             Bank # 2             Bank # 3                 Savings                 Checking       Accounts Payable              Parts              Consultants       Accounts Receivable              Sales              Interest

            Corporation # 1 Corporation # 2

Employee Employee         Salesman # 1 (Salesman # 1)       Sales         Salesman # 2 (Salesman # 2)           Salesman # 1 (Salesman # 1)           Salesman # 2 (Salesman # 2)       Research           Researcher # 1           Researcher # 2 (Researcher # 2) Project Project         Research       Research         Sales           Chemical           Biomedical       Sales           Old Products           New Lines Product Product         Product # 1      Old Product Lines         Product # 2           Line # 1                Product 1                Product 2           Line # 2                Product 3                Product 4      New Product Lines           Line # 3                Product 5                Product 6           Line # 4                Product 7                Product 8 Subsidiary      Subsidiary # 1 (subsidiary # 1)      Subsidiary # 2 (subsidiary # 2)

In the first example of Table 1, legal entity # 1 holds account information, employee information, project information, and product information, thus covering four account parts. Incorporation # 1's account information includes only three components: cash, account payable and account receivable. This legal entity is its salesperson for two types of projects (research and sales) ^. The list of track information is saved, and the list of products is saved. The second example in Table 1 is a bit longer (although still simplified). In this example, the account has a plurality of components hierarchically. Although entity # 2's account has categories of cash, paying accounts, and receiving accounts, each of these categories has subcategories, and some of these subcategories have more subdivisions. Similarly, employee, project, and product information is divided into several categories and subcategories, and entity # 2 has additional items being tracked, such as subsidiaries.

Table 1 suggests that even before considering differences among data sources and / or data storage formats, the structure of a corporation and / or the manner in which it chooses to organize its information will cause differences between one system and another. It illustrates that. For example, if an account has corporation # 1 and corporation # 2 as customers, and wants to use a uniform or standardized reporting and analysis system for these two corporations, corporation # 1 and corporation # 2 Although using the same database software and organizing the accounting information in the software in a similar manner, there is considerable difficulty in doing so. Therefore, using the previous method, in order to provide uniform or standardized reporting and analysis of two legal entities based on the legal entity's database, it usually requires human analysis and understanding of the information in Table 1. .

In connection with still considering accounting information, several forms of information storage can be used to store accounting information of corporation # 1 and corporation # 2. For example, the information may be stored as one or more flat files. Note that, according to at least some usages, storing "flat file" information is not a true database system. Nevertheless, the present invention may, in at least some embodiments, accommodate not only flat file data but also other databases and non-database storage methods.

1 is a schematic diagram showing how a plurality of flat files can be used to store information for corporation # 2 in Table 1. FIG. Although FIG. 1 illustrates the information as being formatted on multiple document sheets, the data is actually stored on a computer readable medium such as a hard disk, for example, as described below. The format of FIG. 1 is intended to illustrate the logical structure of data organized into a number of files 101a-101f, where each file is a file identification shown as title or header information 104a, 104b in FIG. Information 104 and a number of records shown as information lines 106a, 106b, 106c in FIG. 1, each record (organized in columns 108a, 108b, 108c, 108d in FIG. 1); Has a field of Those skilled in the art of programming are well known methods and apparatus for storing and accessing data to have or reflect the logical row and column structures shown in FIG. The present invention can be used in connection with a number of flat file information storage programs. Examples of such information storage programs are programs sold under the trade names " Simply Accounting " and " MAS-90 ".

Data organized in the logical structure shown in FIG. 1 can be stored in a number of different formats. For example, in one embodiment, the data in each flat file 101a-101f is stored as a separate file on the hard disk of the personal computer. Figure 2 shows a directory / file structure that can be used to store such files, where all files shown in Figure 1 are stored in a single subdirectory. As is well known to those skilled in the art, although organized into a directory hierarchy as shown in FIG. 2, various files can be physically stored in a number of independent locations on the hard disk. . Multiple formats can be used to store data in one file, examples of which are shown in FIGS. 3A-3C. In the example of FIG. 3A, the file contains header information, followed by storage of first record 106a, second record 106b, and so forth. In the example of FIG. 3A, a fixed length data format is used in which each record 106a, 106b has the same length 304 (ie, occupies a fixed number of bits). In the embodiment of Figure 3A, each field in each record also has a fixed length 308a-308d.

Figure 3b shows another fixed length data storage method in which data is stored in column order rather than row order (first all dates are consecutive, then types are consecutive). In the embodiment of FIG. 3B, it may be useful to store an indication of the number of records 322 as part of the header, for example, to help locate the desired data. For example, in a fixed length system, as shown in Fig. 3A or 3B, a specific portion of data is arranged at a predetermined distance (at a predetermined number of bits) from the start point of the data. For example, in FIG. 3A, if the header 302 has a length of 4 bytes and the record length 304 is 8 bytes, then the data information for the first record 106a must be at byte number 5. And the data information for the second record 106b necessarily begins at byte number 13.

Figure 3c illustrates the storage of data in delimited fields rather than fixed length fields. In the delimited format, special symbols are used, which are bit patterns different from the patterns used to store data, to distinguish the end or start points of records and / or fields. In the embodiment shown in Fig. 3C, two different special symbols are used, one to distinguish the starting point of the record and the other to distinguish the starting point of the field. These symbols are denoted as colon and semicolon respectively in FIG. 3C, which can be any bit pattern or symbol. In the data format of FIG. 3C, identifying information indicating the data information for the first record 106a as information that follows the first record symbol 324a and before the first new field symbol 324b. It is possible. The data information from the second record 106b is the information that follows the second new record symbol 326a and comes before the next new field symbol 326b. Many other formats for storing information are also possible. It will be apparent from FIGS. 3A-3C that many data storage formats present another problem in accessing, integrating and combining data in different types of information storage systems. Previously, a person wanting to access information directly (without using a database management system or other software to read stored information) may store data, such as in some cases that may be obtained by analyzing an example of stored information. Requires knowledge of the format. Therefore, accommodating the need of an accountant who wants to access the stored information for both corporation # 1 and corporation # 2 in Table 1 relates to the logical organization of data (FIG. 1) and its logical directory structure (FIG. 2). In addition to the information, information regarding the data storage format (Figs. 3A-3C) is required.

In addition to storing information as flat file data, there are many other possibilities. 4A-4F illustrate one possible information organization in relation to the relational database. In the example of Figures 4A-4F, a first transaction table 402 having a plurality of records 406a-406d is stored. The record shown in FIG. 4A is similar to that shown in FIG. 1 in some respects, and includes a data field, a type field, a quantity field, and a total field. In the example of FIG. 4A, an additional index field 408 is provided for each record. In the example of FIG. 4A, the transaction table does not include the header information 104a of the type shown in FIG. 1, and only a single transaction table (not the plurality of tables 101a-101f of the embodiment of FIG. 1) is provided. It is. In the relational database shown in Figs. 4A to 4F, an additional table that can reflect the organization shown in Table 1 is provided. For example, accounting table 412 contains a list of all categories defined in table 1, and index 414 is associated with each account. Similarly, employee table 416 includes the employee name of Table 1, each having an associated index 418. Also in FIG. 4C, for each statement, there is an indication as to whether the person is associated with a sales force and a research force (which reflects the hierarchy shown in Table 1). It also contains a field to indicate the employee's location. Additional tables (not shown) may be provided to list the various projects, products, and subsidiaries of legal entity # 2, reflecting the organization of Table 1.

4D shows a link table 422 for each record in transaction table 402 that indicates the desired link to another table. For example, if the first transaction 406a is a transaction related to the bank # 1 component of a cash account, for a transaction record with index value # 1, a record indicating that there is an appropriate account reference with index # 424 ( 428). Similarly, links may be made to the employee table 416 and other tables (not shown). Therefore, in FIG. 1, it is necessary to provide each file for each possible combination of accounts, subsidiaries, products, projects, etc. (possibly resulting in a very large number of files for comparatively complex accounting structures). In the example of Fig. 1, only a single transaction table 402 is needed in the embodiment of Figs. 4A-4F in which the link table 422 provides information obtained by knowing in which flat file the transaction is stored.

In a typical relational database, it is possible to identify and display only information that meets certain criteria, for example, transactions for specific accounts and specific employees. In some database software, for example, it is possible to store criteria or "queries" for use when optional information is commonly needed. Figure 4E illustrates a table for storing such multiple queries, for example using a structured query language (SQL). Queries used in specific database systems may reflect the way data is analyzed or organized by the company. Therefore, an accountant who may be interested in standardizing reporting and analysis based on information in such a database may wish to be able to know and / or reproduce data analysis in the form represented by various stored queries (FIG. 4E). It may be.

In addition, there are many types of databases that allow users to design reports (for display or print) and, in some cases, to store information that defines such reports, for example for repeated use. have. Accordingly, other tables or sets of tables (not shown) may be stored in association with or as part of a relational database to preserve information about such reports.

The information and structure shown in FIGS. 4A-4F can be stored in many different ways. 5 illustrates a directory / file hierarchy that may be used to store multiple data tables, link tables, query tables, and / or report formats. Such data may be stored in a number of different data formats, such as the format shown in FIGS. 3A-3C or other formats, as will be appreciated by those skilled in the art.

Another example of information that can be stored in various formats is scientific or technical information. 6, a flat file system is provided for storing surface temperature information, for example for meteorological research. In the example of Figure 6, each file 602a, 602b, 602c stores information about a particular location and unit of measurement (e.g., Fahrenheit or Celsius) shown in its header 604. For each record 606a, 606b, 606c, a record of the date and each time is stored in separate fields. 7A-7D, a relational database system for storing this type of data is shown. The data table 702 includes a measurement unit 704a with an index 704b for all observations and for each observation. Table 706 (FIG. 7B) and Table 708 (FIG. 7C) store information about the position and time of day. For a given data point stored in FIG. 7A (as indicated by index value 704b), a link table (FIG. Each line 722, 724 in 7d) may be used. Although the examples of FIGS. 6 and 7A-7D are simplified, those of ordinary skill in the art can store a more complex series of data, such as weather data, radio acoustic data, etc., including wind speed and wind direction. It will be clear how the information system is constructed. If a researcher wants to correlate information from two weather data sources, one source for storing information in the system shown in FIG. 6 and another source for storing information in the system shown in FIGS. 7A-7D. In the case of the previous method, a consultant or other expert typically accesses the information in a manner that allows the combination or integration of the data, analyzing the information storage structure and organization shown in FIGS. 6 and 7A-7D. It was necessary to develop a system manually.

8 is a block diagram of a system according to one embodiment of the present invention for use in overcoming the foregoing difficulties with respect to accessing, integrating, or combining data on different information systems. In the embodiment of Figure 8, the main process 802, as needed in connection with analyzing and / or accessing information in multiple data sources 806a, 806b, 806c, and 806d, provides various drivers 804a, 804b, Selectively activate 804c and 804d. For illustrative purposes, the source data 806a-806d shown in FIG. 8 may be generated by any of a number of programs or systems for organizing or storing data, such as flat file systems, databases, spreadsheets, etc., as described above. It can be stored or generated data. The process and data of FIG. 8 may exist on one or many computers. In one embodiment, this process may be implemented in connection with a local area network (LAN) having a network server computer, associated disks or other storage, and one or more client computers. In one embodiment, the main process 802 runs on a client computer, but the data files for the information source 806 and the new database 808 are stored on a disk (or other data storage) associated with the network server. The invention may be implemented in many different architectures, such as a plurality of non-network computers or a single computer, using a computer that is linked by a communication link, such as a wide area network, modem communication, or the like, via the Internet or the like. To implement the invention, including mainframe or personal computers, such as computers produced by IBM (eg, 386,486, Pentium, or Pentium or higher) and Apple (eg, Macintosh computers) and imitations of such computers, Many types of computers can be used. In one embodiment, the process is implemented using a DOS operating system and / or a Microsoft Windows or Windows 95 user interface.

Items referred to herein as drivers 804a-804d should not be confused with data filters of the type provided in a given database program. A data filter is typically in the form of a query or logical test to select certain records and / or fields, depending on criteria that a user can determine. On the other hand, as will be described more fully below, drivers 804a-804d are processes with a number of functions for analyzing and accessing different types of source data. In one embodiment of the invention, the function module 804 is provided as dynamic link libraries in a manner that will be understood by those skilled in the art after understanding the specification. These drivers 804a-804d are configured for operation with one or more data source types, such as data files created using a particular database program. Depending on the nature of the database program, it may be necessary to have two independent drivers, for example, for data files created by two independent versions of the database software package. In certain circumstances, it may be possible to provide a single driver that can be used in connection with a data file generated using two (or more) different types or brands of software (or a database of a given brand or other software). have.

Source data 806a-806d shown in FIG. 8 can generally be any computer readable information source. Examples include flat file source data, hierarchical databases, relational databases, and spreadsheets. Although Figure 8 illustrates an embodiment in which four data sources are shown, the present invention can be used even when there is only a single data source or there are five or more data sources. Although the present invention can be used in situations where each data source 806a-806d is created using a different type or brand of software, two or more data sources can also be used in the same brand or type of database or in another. It is also possible to use the invention in situations created by software. As one example, the first driver 804a is configured for use in retrieving information from a data file created using "dBaseII", and the second driver retrieves information from a data file created using "dBaseIII". The third driver is configured for use in retrieving information from data files created using a flat file system such as "Simply Accounting", and the fourth driver is "Microsoft Access ™. Can be used to retrieve information from data files created using "

Once the data source has been analyzed (as described more fully below), the result of this analysis is to provide user-access to the information in the data source for review or editing, as part of the data to create a new database. Or all, preferably copying its extension (described below), generating data reports (for review, printing, storage, transmission, etc.), queries, and the like.

In the embodiment of FIG. 8, after the main process 804 performs analysis of the source data 806a-806d using the driver 804, from one or more sources of the various data sources 806a-806d. One or more new databases 808 may be created that contain the data of. In one embodiment, one new database is created for each data source. When such databases have a similar structure, it may be desirable to combine two or more databases, for example, using standard database techniques. In another embodiment, one database 806 uses one database or other data source (e.g., one company stores sales information, and another database or another data source to store employee information). May include information from two or more data sources. The new database 808 may be used to generate a report, for example, using the report writer 810 if desired, and, if desired, for example, the database management system 812 or other. It may be used to enter, review or analyze data using software 814. In one embodiment, the database 808 may include one or more wizards, templates, filters, and / or to provide database reporting and analysis, for example, to output a standard financial report. A Microsoft® Access database that includes base code with toolkit software (these terms will be understood by those skilled in Microsoft Access programming). In one embodiment, the financial and management reporting software is provided as an extension or modification under the trade name MV available from Timeline, Inc., Bellevue, Washington.

Preferably, the analysis system includes a module configured to generate or provide a report or screen for a specific purpose or group. For example, in the embodiment of Figure 8, an executive information system (EIS) preferably has an easy-to-use user interface, and preferably (bar charts and Analyze your data in a variety of spreadsheet, presentation graphics, or printed formats using navigation tools or graphic selectors (to select between pie charts, select reporting intervals, select quarterly vs. weekly reports, etc.) Is configured to output. In one embodiment, the executive is provided with a menu of various data views, including views that can be automatically generated or detected using the automatic rollup generation procedures described above.

In one embodiment, the information in the new database 808 is configured to generate, display or output an analysis or relationship of the data that was not displayed or output by or using the source data 806a-806d, eg For example, it is extended by the main process 802.

9 is a schematic of various drivers 804a-804d. Each driver includes a number of defined processes or functions 901-909. Each function may include computer program instructions 912, for example, to implement and execute one or more steps shown in FIG. 10 described below. In one embodiment, each function 901-909 is a callable subroutine or procedure. The functions 901-909 defined in the predetermined driver 804b include functions that need to be executed or executed differently depending on the type of the source data 806a and 806b. Thus, for example, with regard to function 1 901, which is a function designed to select a predetermined directory on a hard disk or other information storage device where desired information is stored, the procedure for selecting a directory is, for example, the example of FIG. As can be seen from the comparison of the example of FIG. 5 and FIG. 5, it depends on the type of source data 806. Accordingly, the programming code 912 for implementing the function 1 in the first driver 804a may be different from the programming code for implementing the corresponding function in the second driver 804b. In this manner, each driver defines one or more processes to perform one function, which procedure is configured to accommodate different characteristics of two or more different types of source data. For example, FIG. 11A illustrates a portion of a procedure, represented in pseudo-code, in a form that may be used in connection with selecting and / or searching a directory in connection with the directory structure shown in FIG. Shows the corresponding part of the pseudo-code for a procedure that may be used in connection with selecting or searching a directory for the directory structure shown in FIG. One of ordinary skill in the art will understand from the examples of FIGS. 11A and 11B how to configure a driver to perform the same function on two different types of source data. Although FIG. 9 shows a function module having nine functions, the present invention can be used with respect to a function module having more or fewer functions. It is possible for different function modules to define different numbers of functions, and / or to configure a system in which one or more functions are configured to provide or convey null or constant values or information.

Many procedures can be used to begin the method shown in FIG. 10 (step 1002). In one embodiment, the method of FIG. 10 is implemented using a computer program stored on a medium such as a hard disk, CD-ROM, or non-volatile medium, which method is used to launch a program, that is, It is initiated by loading a program into memory and generating commands to the computer (eg, via a keyboard, mask, etc.) to execute the program. Alternatively, this program may be launched by another program. For example, in one embodiment, the new database 808 is a Microsoft Access database, which may include routines such as so-called "wizards" for launching a program, which program (Figure 10), Data in information source 806 is accessed to occupy or update this database 808. In this embodiment, displaying a prompt or "dialog box" for the purpose of requesting user input as needed (e.g., at step 1020) such that the user interface matches a user interface to its database 808. It can be useful to use wizards for this.

In the procedure shown in FIG. 10, the first step after the initiation procedure 1002 is to identify and initialize the dynamic driver (step 1004). In this regard, a driver is considered dynamic in that it can be added or deleted in a modular fashion, for example to accommodate a new or other type of data source. For example, a user may initially have a system such as the one shown in Figure 8 with four drivers, but in the future, it may be purchased from a software vendor, downloaded through an information service, a network, an internet connection, or the like, or You can add additional drivers by writing a custom driver. Due to the module or dynamic characteristics of the driver, it is not known in advance which drivers are available, and therefore, when the program is started (step 1002), the program identifies the drivers available to it. In one embodiment, this is done by searching the disk or its directory for a file with a given (partial) file name or file extension. In one embodiment, the program may also analyze selected portions of each file, such as, for example, header information, to verify that the file identified by such file name and / or file extension is the desired driver. have. Initializing a driver generally includes identifying and linking driver functions and initializing data within each driver.

Next, it is determined whether the procedure will perform an import or update (step 1006). In the case of import, a procedure is first performed in which all or most of the data and structures in the data source are accessed and stored in a new database. In the case of an update, only selected portions of the data and / or structure are accessed, for example, to ensure that the information in the new database 808 reflects recent changes or additions that may have been made to the data source 806. Procedure is performed. In a typical situation, an import will be performed first when the system of FIG. 8 accesses or uses information from a given data source, or when relatively significant changes or additions have been made to that data source. Typically, the update will be performed in a regular manner (eg, daily or weekly) to synchronize the data in the source data 806 with the data in the new database 808. In one embodiment, the selection for import or update (step 1006) is performed automatically by performing the update unless the procedure is the first to access a particular data source. In another embodiment, the user is allowed to choose between import and update, for example, by providing input through keyboard selection or using a pointer device.

If import is selected (step 1008), main process 802 will begin execution of one or more driver functions to select a directory to search (step 1010). The driver 804 loaded or called by the main process 802 depends on what type of data source is accessed. In particular, for a given data source 806a, the main process 802 will use a driver 804b configured to receive that type of source data 806a. If more than one data source 806 is accessed, the main process 802 will use a driver 804 configured for each type of source data 806 in either case. The type of data source is preferably determined automatically based on characteristics such as the name of the file and / or directory (or "extension"), the number, size and structure of the file, the header or other information within the file. In another embodiment, the user may identify the brand name and version number of the software used to generate the data source file (e.g., or if the user wants to search only local disk files by the procedure or network). Allowed or required to indicate the type of data source) by indicating whether it wishes to perform a search comprising the file. After the end of step 1010, the main process 802 will access a stored list of directories to be searched for all data sources 806 as identified by the driver 804 identified in step 1004. . After step 1010, the main process 802 loads, activates, or calls another function 902 of the function modules 804a-804d to search the directory selected in step 1010 for the data to be imported. (Step 1012). The search of the directory (step 1012) is performed in a manner that will depend on how the information is stored at different data sources 806. For example, for some form of source data, it may be sufficient to identify a file with a given file name and / or a given file extension. For other forms of data source 806, it may be necessary, for example, to scan the data in the various files to identify a file having a predetermined structure or content in the header portion of the file or elsewhere. Therefore, different modules 804 are configured to provide a "directory search" function 902 in different ways to accommodate different data sources 806.

If an update (step 1014) is performed rather than an import (step 1008), preferably, when the import is performed for the first time, the result of the functions 901,902 for selecting and navigating the directory is later sent to the main process 802. Because they are stored in a way that can be accessed by them, there is no need to select and navigate a directory. Therefore, using this stored information, the main process 802 can identify previously imported or updated data. In one embodiment, this is useful to prevent loading redundant data, that is, data that already exists in the new database 808. In general, for a full update, in step 1016 it is desirable to identify new or changed data after the last import or update so that at least some existing data in the database 808 is not reloaded. Do. In one embodiment, to prevent loading of redundant data, the system attempts to identify data that has not changed since the last import or update. In general, if such a procedure is involved, the data in the new database 808 at the end of the procedure is synchronized with the information in the source data 806, i.e., this is the data source 806 in its current state. Will contain information that accurately represents the structure and data of the.

In the embodiment of Fig. 10, the identity of the data to be imported or updated is displayed in order to give the user an opportunity to select the data to be imported or updated, or to choose to stop importing or updating the given data (step). 1018). The manner in which the indication of data to be updated or imported is organized for display depends on what type of data source is accessed and, thus, is provided in response to the invocation or activation of function 902a of one of the drivers 804. Will be. For example, a function 902a of a driver configured for use in connection with the data source shown in FIGS. 4A-4F gives a user an opportunity to import or update data for some company, except for another company. A list of subsidiaries obtained from table 430 (FIG. 4F) may be displayed for presentation. Preferably, the user can select one or more companies from the displayed list. The display in the selection steps 1018 and 1020 may, for example, select the data specified for a given employee 416 or a given account 412, depending on how the display function 902a of the driver is recorded or configured. It may be repeated for other forms of organization or data in the data source to display and allow.

As described in more detail below, in some cases, after a new database 808 has been created, the user can create, save, edit, and in some cases, the original information source 806a- to review the data. 806d) will continue to be used. Therefore, the present invention is also compatible with situations where a user wishes to continue to use a database 806, user interface, etc., which is already familiar to the user. However, in this case, the new database 808 is sometimes updated to reflect new or edited data in the information sources 806a-806d that occurred after the new database 808 was first created (or last updated). It is desirable to. One way to perform this update is to repeat the entire process of creating the database 808 (as described below). However, in many situations this is inefficient because a significant portion of the initially created new database 808 remains unchanged and still valid. Therefore, in accordance with one embodiment of the present invention, a procedure is provided that allows a new database 808 to be updated only for data from information sources 806a-806d that have changed since the last update of the database 808. .

The frequency with which a new database 808 should be updated depends on the frequency with which various uses of that database 808 are made. Therefore, updating the database 808 every day may not make much sense if it is accessed only once a week. In addition, the specific information included in the update may vary depending on the use made to the new database 808. Therefore, if factory production data is only reviewed quarterly by management, there is no need to include such data in a weekly update that may be used, for example, to review local sales. It is desirable that one or more profiles defining various types of updates be created and stored, and also that a scheduler be created and stored. The scheduler is used to define when to automatically execute such an update (without the need for a person to "calendar" or remember to initiate such an update). Preferably, for example, different updates are provided, such as providing a scheduler that automatically executes a regional sales update procedure once weekly prior to a weekly sales meeting and schedules a quarterly update of production data prior to a quarterly production review. Profiles are scheduled to run at different times or intervals.

Others using the system of FIG. 8 may use other components of the system (e.g., information sources 806a-806d or new database 808) for daily operations, so that profiles 822 with the new database may be used. ) May be stored, or the profile 824a-824d (if the information source 806a-806d has the appropriate "record permission" to store the information) with the previous database, or both together. May be stored.

Various methods can be used to create the profile. Including commands (such as menu options or buttons) to allow the user to request the creation of an update profile (for example, via a predefined set of screen formats or dialog boxes, such as those provided in the Microsoft Access Wizard). It is possible. Further, for example, whenever a user requests a screen or printed report that uses data that is not currently in the defined file (or uses the data more frequently than the current profile update frequency for that data), the user requests a profile. It is also possible to automatically urge you to make a decision regarding the creation or editing of a. In one embodiment, fill in each field of database 808 and, for each field, whether there is an existing profile for updating that database, the identity or name of such profile, and the current update frequency or interval. By creating a database table to display, profile 822 is generated.

In addition to the automatically scheduled update, the user of the system of FIG. 8 is also preferably provided with the option to request an update at any time, and also preferably to select from a predefined update profile or request a full update. Option is provided. If desired, the system may prompt the user to make a decision as to whether this data set to be updated should be stored as a profile (as described above). The system may also provide a list of already existing or defined profiles so that the user can select from predefined profiles rather than select from displayed data (such as a list of subsidiaries).

In some cases, it may be predetermined that it is desirable to always import or update (front update) all information available from the data source, so that the function 902a for the applied driver merely passes the program flow to the main process ( Return to 802. For example, with respect to the data source shown in FIGS. 7A-7D, it may be determined that all available indicator temperature data from all locations is always included in every import or update. In one embodiment, a display may be provided to the user indicating the location of data corresponding to the user's selection, such as the display of directories, subdirectories, and files containing information, and optionally, any directory and file. Opportunities may be provided to choose whether or not the back will be accessed.

Once, for example, by step 1018, 1020 it is determined which data is to be imported or updated, general information is loaded at step 1022. If it is desired to access information from two or more data sources, this is performed in series (ie, steps 1022-1046 for the first data source using the first module, and then). By performing steps 1022-1046 on the second data source using an appropriate driver, or in parallel (ie, using an appropriate driver before performing a later step on each information module). By performing the steps for the desired data source).

General information includes information about the structure of the data in the data source. The form of general information loaded in step 1022 will vary depending on the various forms of source data. For example, in a function 903 recorded or configured for use in connection with a database such as that shown in FIGS. 4A-4F, the general information may be, for example, an account or other category used in the data source 806. It may also include your identity. On the other hand, if the function 903 is recorded or configured for use in connection with the data source shown in Fig. 1, it may still be required to determine how many components are used in the data source, but in this case This information will be determined by the number of flat files 101a-101f found in the data source 806. The general information may also include information such as how many projects 112, how many products 114 and / or product lines 116, or how many subsidiaries 118 are defined in the data source 806. Can be. The general information can also be loaded at a time (as opposed to the company name, the first month of the fiscal year, and, in general, the information that is loaded in steps 1024, 1033, 1036, typically loaded in a loop). May contain other information that may be present. If the " general information loading " function 903 is provided to a driver configured for use in connection with the data source shown in Figure 6, then general information such as the number of locations 602 in the database can be loaded in step 1022. Can be.

The main process 802 may also call or activate the function 904 of the appropriate driver or module 804 to load the data definitions. Data definitions are stored as identifiers for specific classes or categories of data in data source 806, text names stored, field sizes, types of data (strings, integers or decimal numbers, decimal digits), and various categories of data. Information such as similar characteristics can be included. Preferably, the loading of data definitions is as required to create one or more new databases 808 that will contain all the structures and data necessary for the type of reporting or analysis to be performed on the new database. Interrogation of the data to obtain the information necessary to store an indication of the architecture or structure of the data element within and the information within the data source. The querying of data in the "loading data definition" phase is an intelligent query in that it can be matched to virtually any data source and can identify what is required to store the standard format of the data source, for example for reporting and analysis. to be. In the example of Figures 4A-4F, the information needed to indicate the architecture of the source data is for example stored in a given string account part as well as the names of four account parts (account, company, employee and location). It also includes the data type (eg, numeric or string) and length needed. In the example of Figure 6, the information needed to indicate the architecture of the data source includes storing the name (unit and date) of the criteria used for that data as well as the name (location and date) of the account portion. The query may include identifying other optional data that may be loaded, such as, for example, an invoice number. The particular type of query that is performed will depend on the characteristics of the particular data source being analyzed and, therefore, depends on each driver 804. In general, the steps of loading data or information (1022, 1024, 1033, 1036) are performed by a function in the driver 804, and saving the information (1026, 1028, 1030, 1032, 1034, 1038) Performed by the main process 802.

The main process 802 then identifies or creates a database repository (step 1026), i.e., a new database 808 that acts as a location from which information loaded from the data source 806 will be saved. Identify or create a file or other data storage structure within. Updates typically do not require creating a new database or database table, because updates are typically simply adding to existing tables in an existing database.

Next, the main process 802 invokes the appropriate function 905 of one or more drivers to create a database table that will be used to store the saved data from the source data into the new database 808 (step). 1028). The manner in which the database tables are created preferably takes into account the data source 806 and the structure of the data and the manner in which the new database 808 will be used, for example for analysis, report generation, and the like. Since the particular table created varies according to the nature of the information in the data source 806 (eg, as determined by steps 1022 and 1024), creating a database table (step 1028) provides access. Function provided by the driver 804 configured for the particular database used for the purpose. For example, if the "create database table" function 905 is written or configured for use in connection with a data source as shown in Figures 4A-4F, the generated database table may be, for example, an account table. , An employee table, a subsidiary table (which may be a rollup of the account), and a detail table (described in more detail below), while using in connection with the database shown in FIGS. 7A-7D. The "create database table" function written to or provided to a driver configured for this may include a location table, a date table, a time table, a unit table and a detail table. Preferably, a table created in the new database 808 has a dynamic structure or architecture in that it can accommodate virtually any form of data definition or structure that may be found in various data sources 806. In one embodiment, the new database 808 is intended to be used primarily for outputting information, such as generating reports and analysis, and therefore, as described below, high in the form of available output and data analysis. It is desirable to be configured to provide good output performance, such as flexibility and relatively fast execution of such analysis and / or output. In this regard, if one database provides a speed or flexibility of output that is better than the speed or flexibility of any other possible configuration, it is optimized for the speed and / or flexibility of the output. Thus, in this regard, "optimized" does not necessarily require mathematically accurate optimization. In one embodiment, in step 1028, three general types of tables are provided, namely a plurality of category tables (including rollup tables, where appropriate), at least one detail table and at least one entry table. . Preferably, a category table is provided for each manner in which a particular data point or record can be sorted. For example, if the " create database table " function 905 is provided in a driver 804 configured for use with a database as shown in Figs. 4A-4F, then as shown in Fig. 12, a new database is shown. For example, an account table 1203 that lists all possible account categories of an account, a subsidiary table 1230 that lists all possible subsidiaries found in the data source 806, and all products noted in the data source 806. A product table 1232 for filling out an employee table, an employee table 1216 for filling out all employees paying attention in the data source 806, and a location table for filling out various locations, sales regions, etc., which are noted in the data source 806; Will include a plurality of category tables 1202. In the illustrated embodiment, each record or item in each category table 1202 is associated with an index for use in the details table as described below.

In the embodiment shown in FIG. 12, once occupied, a detail table 1240 is provided that will have a record for each accounting entry or transaction at the data source 806. In the embodiment shown in FIG. 12, for field 1244, a date field 1242b, a kind field 1242c, a quantity field 1242d, and a total field, corresponding to a transaction (FIG. 4A) at the data source. 1242e is provided. An index field 1242a is also provided for storing an identifier number or an index number for each record. In addition, for each record, including the account category 1242f, the subsidiary category 1242g, the product category 1242h, and the employee category 1242i, as defined in the general information loading step 1022 in the example of FIG. Independent fields are provided to store an indication of the appropriate information for each category. In general, it is desirable to provide as many different fields, or categories, as are present in the data source 806 as needed to analyze or compute the data. Therefore, it is useful to have an account category because it may be desirable to output a report that groups the transactions according to the account with which the transaction is associated. In addition, depending on the desired accounting purpose, it may be desirable to print an independent report for each subsidiary or to print a report in which transactions are grouped by subsidiary, thus having a subsidiary category 1242g. In general, separate fields may be provided in the detail table 1240 for each method of selecting, grouping, reporting, printing, or analyzing data.

The structure of the database shown in FIG. 12 may differ significantly from the structure of the data source shown in FIGS. 4A to 4F and the structure of the data source shown in FIG. For example, in the structure shown in Figs. 4A to 4F, the manner in which a specific transaction (Fig. 4A) is associated with a specific account (Fig. 4B) is shown in an independent link table (Fig. 4D). The index for the appropriate account 1242f is then stored in its own field 1244 of the same record containing the transaction information. Therefore, although a database 808 having a table as shown in Fig. 12 is a data source as shown in Fig. 1 or a data source (or other configured data source) as shown in Figs. 4A to 4F. Although the information found in FIG. 12 may be stored, the structure or architecture of the database of the example of FIG. 12 is different from that of the data source shown in FIG. 1 or the data source shown in FIGS. 4A-4F. Similarly, although the form of the information stored in the two structures of FIG. 12 and FIG. 1 is similar, the relational database structure of FIG. 12 differs from the flat file structure shown in FIG.

The main process 802 is generic (loaded in step 1022), for example, to additional tables provided in the database 808, for example for use in later steps and / or later updates of FIG. And save the information (step 1030) and save the data definition (loaded in step 1024) (step 1032).

The main process 802 is responsible for loading one or more drivers 804 to load the data definition code (eg, field width, data type, etc.) for the table created in step 1028 into the new database 808. Use function 908. In one embodiment, rollup information is also loaded at this time. In general, rollup information refers to information used to define a sub-category of data, that is, a group of items within a category table. By way of example, as shown in FIG. 12, an employee category table may be associated with a location or region, for example, to identify a location or site or region where each company employee is placed or responsible. For example, a company may have many sales employees associated with one sales territory. As another example, various products of one company may be rolled up or grouped into a product line. By defining a field 1238 for the location rollup code, the structure of FIG. 12 makes it possible to output a report grouped by sales territory. Rollup can also be used to provide statistical analysis of group data such as mean values, standard deviations, and the like. Although in the embodiment of Figure 12 the field 1238 for the location rollup code is shown to be a field of the employee's category table 1216, this location field 1238 may also be provided in the details table if desired. It may be.

The way the function 908 for loading the rollup code operates depends on the type of source data 806 configured to work with it, so that different programming instructions may be used for use with different types of source data. It is provided as a function of various drivers 804 to be provided. As an example, a “roll up code definition” function 908 may be provided to a driver 804 configured for use in connection with the database shown in FIGS. 4A-4F. In this example, the location field is already defined in the employee table 416, which can be used directly for location code purposes. In contrast, in the embodiment shown in FIG. 1, there is no indication of the location for employee 120 associated with the particular flat pile 101a. Therefore, in one embodiment, position rollup for data obtained from the data source of FIG. 1 may not be possible. However, if, for example, another file exists that provides a home address for each employee in the company, for example, it estimates the sales region to which the individual can be responsible and, therefore, speculatively defines the location rollup code. In order to do so, it may be possible to use the residence status of each salesperson. The "roll up code definition" function may also include access to information that can be used to define the roll up code. For example, with respect to the data source shown in Figure 6, the "roll up code definition" function 908 creates a table for each positional temperature station that indicates whether the station is a northern hemisphere station or a southern hemisphere station. It can be included in a function, and thus, hemispheric rollup code can be generated based on such a thing. In some cases, it may be desirable to provide word recognition and / or search for keywords in a database to define additional rollup and / or structure.

In some situations, the rollup code is associated with information not used in the data source as a basis for analyzing or grouping the data (eg, as a hemisphere rollup code for the data source of FIG. 6). Therefore, in such a situation, providing a rollup code involves providing an extension of the data by automatically providing additional elements that are not available (or at least not used) for outputting or analyzing the information in the data source 806. do. The data is preferably classified and grouped into categories by a thorough analysis of the data of the data source.

The system can be configured to recognize and add certain reporting relationships that can be determined by the degree of definiteness that depends on the data in the information sources 806a-806d or the structure of the data. For example, sales information may include sales organized by sales region (obvious in information sources 806a-806d or estimated using salesperson addresses as described above). These regions may also be two or more sales regions, if, in accordance with one embodiment of the present invention, the vice president's relationship to that sales region may be apparently found or estimated from information sources 806a-806d. It may be reviewed or analyzed by other groups, such as by two or more vice presidents responsible for

Preferably, such additional rollup or extension is defined only if the data indicates that it may make sense to review the data according to rollup criteria. For example, in one embodiment, the extended or additional relationship is automatically automatically, unless there is one or more values for that field or parameter, preferably less than the number of records containing that particular field or parameter. Not added. For example, if there are two different vice presidents who are responsible for different regions, it may make sense to investigate sales according to the sales volume corresponding to each vice president. However, in the example of Figures 6 and 7, if all reporting stations are located in the tropics, the system will not automatically generate rollups or extensions to review weather data according to snowfall categories. This is because in this example, all stations will report zero for snowfall. Thus, for an office database, the system preferably checks the data in the source databases 806a-806d to determine if there are, for example, one or more salespeople, one or more regions, and / or one or more products. If there is more than one value in one field for various records in the database, the system may enter the field, for example, as grouped by the average or sum of the values (eg, sales average or sum, cost, etc.). Accordingly can be configured to automatically provide an option for reviewing the data. In one embodiment, this is realized by creating a Microsoft Excel "pivot" table.

As an example, referring to FIGS. 4A-4E, the table of FIG. 4D may be used to determine, for a given transaction, which employee is associated with that transaction. 4C can be used for a given employee to determine if the employee is associated with a northwest region, a southeast region, or a central region. If all transactions are associated with employees in the central region, there is no meaning in displaying transactions by region. However, if a transaction in the table of FIG. 4D is associated with employees in at least two different regions, the system may average or sum (and / or from FIG. 4B) transactions classified by location or region associated with the employee associated with the transaction. Can be configured to automatically generate a rollup that displays a particular account type of transaction as determined.

In addition to defining rollups, this process can also store optional reference fields. In general, an optional reference field refers to a field that is not normally used to group data, such as a pre-text field (comment, memo field, invoice number, etc.), although it may be required to include it in the report.

After loading of the data definition codes and rollups, these data definition codes and rollups are saved to the new database 808, for example by writing the categories into the various category tables 1202 (step 1034). The loading and saving of the data definition and rollup code in steps 1033 and 1034 is performed in a looped manner to load and save a specific category (in the example of FIGS. 4A-4F, a specific account, company, employee and location). (Step 1035).

Looking back, in accordance with the illustrated embodiment, step 1024 defines the category (eg, account, company, employee and location) as well as its data type (eg string or numeric value). Step 1028 generates the category table defined in step 1024 (and other tables defined in step 1022). Step 1032 saves the data definition to one standard table. Steps 1033 and 1034 load and save the data definition and rollup code.

At this point in the process, although information related to the data structure has been placed in the new database 808, the data that is the subject of the source data 806 (e.g., accounting entries or transactions in the case of accounting source data, Case temperature data) has not been loaded into the new database 808. Thus, the main process 802 calls or activates the function 909 in the appropriate driver 804 to load data (step 1036), save the data (step 1038), and load all desired data to be saved. The process is repeated until step 1040, step 1039. Therefore, at the end of this procedure 1036, 1038, 1040, the new database 808 is occupied by data from one or more data sources 806.

When two or more data sources having different structures and / or created using different brands or types of software are combined using the procedure of FIG. 10, the data from these different types of sources may, for example, It may be occupied within a common database structure as shown in FIG. This facilitates common or standardized analysis and reporting on data, preferably optimized to provide flexibility and speed of output.

In the embodiment of FIG. 10, main process 802 can now build data queries, such as summarization queries, and execute if desired. In general, there are at least three types of queries that can be built. A first type of query that is common to all new databases 808 created using the procedure of FIG. 10, such as a query that provides the number of entries in a detail table or the number of entries for a given data range. Can be provided. Other queries may be built, at least in part, depending on the data definitions and general information obtained about one or more data sources 806, including rollups that may have already been provided, and, if desired, It may be provided as part of the driver 804 specific to the data source. A third form of query may be provided to duplicate or include a query or report used in the original data source (eg, as shown in FIG. 4E).

After the new database 808 is occupied, the system will automatically perform some audit or inspection of the data, according to one embodiment, to verify that the system is operating properly. Various forms of testing may be included. To verify that the data has not been modulated, data samples of the new database 808 can be compared with corresponding data in the sources 806a-806d. In addition, a new database 808 can be checked to verify that the required structure exists. For example, in the case of an accounting database, the new database 808 may be automatically checked to determine if the required account portion exists. The new database 808 can be checked for an empty set, such as to ensure that rollups or other defined extensions are not empty.

Once the new database 808 is occupied and verified and the appropriate query is built, the main process 802 can close the table and database (step 1044) and close the dynamic driver, for example to free memory. (Step 1046).

Although the present invention has been primarily considered for use in connection with providing standardized and / or extended reporting and analysis of data in one or more data sources, a database management system (eg, Microsoft) in connection with a new database 808. It is also possible to use the present invention for data entry and data storage using Access, Excel, FoxPro, Btrieve, etc.). Although the primary use of the present invention is to entail continuing to use the original source data 806 for input and storage, while maintaining the same copy of information in a new database 808 for reporting and analysis purposes. However, as described above, the data is first stored in a new database 808, and then the information from the new database 808 is downloaded or exported to another form of source data 806c, thereby providing one type of source data ( It is also possible to use the present invention to transfer data from 806a, 806b to other forms (eg, 806c).

In view of the foregoing description, many advantages of the invention can be appreciated. The present invention facilitates standardization of reporting and analysis despite the variety of brands or forms of data used. The present invention provides a system that can provide optimized or improved performance in outputting or reporting data. The present invention also provides extended data reporting and analysis capabilities over data reporting and analysis of data sources. Through more complex queries of source data, in connection with an accounting system, the present invention may reflect a chart of accounts set up in the data source. In one embodiment, the process extracts some or all of the defined information, such as rollup, optional reference fields, fiscal period information, and the like. By performing the task automatically and eliminating (or reducing) the need for human analysis, the present invention is less labor-intensive and less time-intensive than the previous method, and in some cases, by the previous method. Makes it possible to occupy a new database 808 in minutes or hours in situations that require days or weeks. In one embodiment, the driver 804 may be configured to detect, analyze, and maintain in the new database 808 security, passwords, permissions, etc. used at the data source 806. In this manner, the system administrator does not necessarily need to maintain a new, separate set of accounts, passwords, permissions, etc., in the new database 808 in addition to being maintained by the original data source 806. Preferably, the system can be configured to perform updates at substantially predetermined intervals, such as daily, weekly, or the like.

Various modifications or variations of the present invention can also be used. It is also possible to use only some aspects of the invention without using other aspects. For example, it is also possible to occupy a new database 808 without defining new or additional rollups. Although in the foregoing description, various drivers 804 can be provided as separate DLL files, and can be added as desired by simply storing additional DLL files in the appropriate directory, the functions stored by the function modules are independently stored modules It is also possible to make a viable version of the invention provided as a subroutine or part thereof, which is called by the main process 802.

Although the present invention has been described using the preferred embodiments with certain variations and modifications, other variations and modifications may be employed and the invention is defined by the appended claims.

Claims (53)

A computer-implemented method that can be used in connection with accessing data that can be stored in one of the first and second different data sources, Providing a first driver comprising program instructions configured for use in association with the first data source; By automatically accessing the content of the information stored in the first data source, thereby automatically obtaining first information about the data structure of the first data source without requiring human analysis of the first data source. A second step of using the first driver; And Using first information to define a structure for a first database, wherein the structure for the first database is different than the structure of the first data source, and the structure for the first database is also the second Also different from the structure of the data source, the first database does not exist prior to the step of using the first driver to automatically obtain the first information. How to include. The method of claim 1, Using the first driver to store at least some information from the first data source in a first database How to include more. The method of claim 2, The first data source provides a first data analysis, The method further includes the step of providing data analysis in the first database that is different from the first data analysis. Way. The method of claim 1, The first driver includes programming code callable by the main process, The method may be extended for acceptance of the second data source by providing and invoking a second driver comprising program instructions configured for use in connection with the second data source in the absence of substantial modification of the main process. Extensible Way. The method of claim 1, The method further includes providing a third driver configured for use with at least one readable data source different from the first data source, without the need to modify the first driver. Way. A computer that can be used in connection with accessing data that may be stored in one of a first and a second different data source, wherein at least one of the first and second data sources is configured to generate at least a first output. In a method implemented, Providing a first driver comprising program instructions configured for use in connection with the first data source; Providing a second driver different from the first driver, the programming code configured for use in connection with the second data source; Using the first driver to obtain first information about the data structure of the first data source by automatically accessing content of information stored in the first data source, and relating to the data structure of the second data source. Using the second driver to obtain second information; Using the first and second information to define a structure for a first database different from the first and second data sources, wherein the first database is configured to obtain the first and second information. Does not exist prior to the step of using the first and second drivers; And Using the first and second drivers to store at least some information from the first and second data sources into the first database. How to include. The method of claim 6, Generating at least a first report based on the information in the first database How to include more. The method of claim 7, wherein The method further includes providing an additional report at the first output that is different than the first report. Way. The method of claim 6, Each driver contains program instructions for performing a number of functions. Way. The method of claim 6, The first database is optimized for the speed of data output Way. The method of claim 6, The first database is optimized for flexibility of data output Way. The method of claim 6, The first database includes a plurality of category tables, at least one detail table and at least one entry table. Way. At least one of a first and a second different data source, wherein at least one of the first and second data sources is configured to generate at least a first output. In Coupled to the first and second data sources, the following steps, i.e. Providing a first driver comprising program instructions configured for use in connection with the first data source; Providing a second driver different from the first driver, the programming code configured for use in connection with the second data source; Using the first driver to obtain first information about the data structure of the first data source by automatically accessing content of information stored in the first data source, and relating to the data structure of the second data source. Using the second driver to obtain second information; Using the first and second information to store third information on a data storage medium, wherein the third information describes a structure for a first database, the first database being the first and second information. Does not exist before using the first and second drivers to obtain information; And A computer programmed to perform the step of using the first and second drivers to store at least some information from the first and second data sources into the first database. Device comprising a. An apparatus that can be used in connection with accessing data that can be stored in one of the first and second different data sources, First driver means including program instructions configured for use in connection with the first data source; Second driver means different from said first driver means, including programming code configured for use in connection with said second data source; Using the first driver to obtain first information about the data structure of the first data source by automatically accessing content of information stored in the first data source, and relating to the data structure of the second data source. Means for using the second driver to obtain second information; Means for using the first and second information to define a structure for a first database, wherein the first database uses the first and second driver means to obtain the first and second information. Does not exist before-; And Means for using the first and second driver means to store at least some information from the first and second data sources into the first database. Device comprising a. A computer program that can be used in connection with accessing data that may be stored in one of a first and a second different data source, wherein at least one of the first and second data sources is configured to generate at least a first output. In a computer-readable medium storing the information, The computer program has the following instructions, Instructions for providing a first driver comprising program instructions configured for use in connection with the first data source; Instructions for providing a second driver different from the first driver, the programming code configured for use in connection with the second data source; Using the first driver to obtain first information about the data structure of the first data source by automatically accessing content of information stored in the first data source, and relating to the data structure of the second data source. Instructions for using the second driver to obtain second information; Instructions for using the first and second information to define a structure for a first database, wherein the first database uses the first and second drivers to obtain the first and second information. Never existed before; And Instructions for using the first and second drivers to store at least some information from the first and second data sources into the first database. Computer-readable media. In a computer implemented method, Providing a driver for generating instructions for accessing data that may be stored in one of the first and second different data sources, wherein the driver is configured to execute program instructions configured for use in connection with the first data source. Includes-; By accessing the content of the information stored in the first data source, the driver is used to automatically obtain information about the data structure of the first data source without requiring human analysis of the first data source. Step, wherein the information about the data structure leads to optimization of the new database in which information from the new database is stored. How to include. A computer-implemented method that can be used in connection with accessing data that can be stored at a first data source, Providing a driver comprising program instructions configured for use in association with the first data source; By automatically accessing the content of the information stored in the first data source, thereby automatically obtaining first information about the data structure of the first data source without requiring human analysis of the first data source. A second step of using the driver; And Using the first information to define a structure for a first database that is different from the data source, wherein the first database is present prior to using the first driver to automatically obtain the first information. Without causing the first information to lead to an optimization of the first database where information from the first data source is stored. How to include. The method of claim 17, The first data source stores accounting information, wherein the first information includes an identification of an account portion. Way. The method of claim 17, Storing data from the first data source in the first database How to include more. The method of claim 17, Verifying information stored at the first data source How to include more. The method of claim 19, Modifying at least some data stored in the first database to provide modified data, and writing back at least a portion of the changed data to the first data source How to include more. The method of claim 19, Creating a second database and storing at least some data stored in the first database into the second database How to include more. The method of claim 22, Generating the first and second databases includes creating a database table in consideration of the manner in which the first and second databases will be used. Way. The method of claim 22, The first data source provides a first data analysis, The method further includes the additional step of providing data analysis in at least one of the first and second databases different from the first data analysis. Way. A computer-implemented method that can be used in connection with accessing data that can be stored in at least a first data source configured to generate at least a first output, the method comprising: Providing a driver comprising program instructions configured for use in connection with the first data source; Using the driver to obtain first information about a data structure of the first data source by automatically accessing content of information stored in the first data source; Using the first information to define a structure for a first database that is different than the first data source, wherein the first database does not exist prior to the step of using the driver to obtain the first information. The first information causes optimization of the first database; Using the driver to store at least some information from the first data source into the first database; And Updating the first database with less information than all the information in the first data source, wherein the updating step includes storing the first database to store at least some information from the first data source into the first database. Performed after step using driver- How to include. The method of claim 25, The updating step uses at least a portion of the first information. Way. The method of claim 25, Repeating said updating step, wherein data in said first data source is synchronized with data in said first database- How to include more. The method of claim 25, Creating a second database and storing at least some data stored in the first database into the second database How to include more. The method of claim 28, Generating at least a first report based on information in at least one of the first database and the second database. How to include more. The method of claim 29, The method further includes providing an additional report at the first output that is different than the first report. Way. In a computer implemented method, Providing a driver for generating instructions for accessing data stored at a first data source, wherein the driver includes program instructions configured for use in connection with the first data source; Using the driver to automatically access content of information stored in the first data source to obtain first information about the first data source without requiring human analysis of the first data source. ; Creating at least a first database to store at least some data from the first data source, wherein the first database is based on at least a portion of the first information, the first information being the first information; -Leads to optimization of the database; And Creating at least a second and third database comprising information from the first database, wherein the second and third databases are different from each other; How to include. An apparatus that can be used in connection with accessing data stored in a first data source configured to at least generate a first output, the apparatus comprising: Coupled to the first data source, the following steps, i.e. Providing a driver for generating instructions for accessing data stored at the first data source, wherein the driver includes program instructions configured for use in connection with the first data source; The first driver may be configured to automatically access content of information stored in the first data source to obtain first information about the first data source without requiring human analysis of the first data source. Using; Creating at least a first database to store at least some data from the first data source, wherein the first database is based on at least a portion of the first information; And A computer programmed to perform at least a second and third database comprising information from the first database, wherein the second and third databases are different from each other. Device comprising a. A computer usable in connection with accessing data that may be stored in one of a first and a second different data source, wherein at least one of the first and second data sources is configured to generate at least a first output. A computer-readable medium for storing a program, the method comprising: The computer program, Instructions for providing a driver for generating instructions for accessing data stored at the first data source, wherein the driver includes program instructions configured for use in connection with the first data source; The driver is configured to automatically access content of information stored in the first data source, without requiring human analysis of the first data source, to automatically obtain first information about the first data source. Instructions for use; Instructions for creating at least a first database for storing at least some data from the first data source, wherein the first database is based on at least a portion of the first information, the first information being the first information; 1 led to the optimization of the database-; And Instructions for creating at least a second and third database comprising information from the first database, wherein the second and third databases are different from each other. Computer-readable media. An apparatus that can be used in connection with computer-implemented access to data that can be stored in one of the first and second different data sources, A driver comprising program instructions configured for use in connection with the first data source; By automatically accessing the content of the information stored in the first data source, thereby automatically obtaining first information about the data structure of the first data source without requiring human analysis of the first data source. Means for using the driver; And Means for using the first information to define a structure for a first database that is different than the data source, wherein the first database exists prior to the step of using the driver to automatically obtain the first information. Never- Device comprising a. The method of claim 34, wherein The first data source provides a first data analysis, The apparatus further includes means for providing data analysis in the first database that is different from the first data analysis. Device. The method of claim 34, wherein Each driver contains program instructions for performing a number of functions. Device. The method of claim 34, wherein The first information about the data structure includes information from queries stored in the first data source. Device. The method of claim 34, wherein The first data source stores accounting information, the first information comprising an identifier of an account portion Device. In a computer implemented method, Providing a driver for generating instructions for accessing data that may be stored in one of the first and second different data sources, wherein the driver is configured to use in connection with the first data source. Including-; By accessing the content of the information stored in the first data source, mapping at least some of the information in the data source to a process for providing a corresponding item in a new database, thereby requiring no human analysis of the first data source. Using the driver to automatically obtain information about the data structure of the first data source, wherein the information about the data structure is selected from the new database in which information from the first data source is stored. Led to optimization-; And Generating a report from the new database How to include. A computer-implemented method that can be used in connection with accessing data that can be stored in one of the first and second different data sources, Providing a first driver comprising program instructions configured for use in connection with the first data source; By automatically accessing the content of the information stored in the first data source, thereby automatically obtaining first information about the data structure of the first data source without requiring human analysis of the first data source. A second step of using the first driver; Using the first information to define a structure for a first database that is different from the data source, wherein the first database is present prior to using the first driver to automatically obtain the first information. Not-; And Generating at least a first report based on the information in the first database How to include. A computer-implemented method that can be used in connection with at least a first data source that stores first source data, wherein the first source data includes accounting data, the accounting data having a plurality of account portions. Used according to Using a computer to automatically obtain information about the data structure of the first data source, without requiring a human analysis of the first data source by accessing content of information stored in the first data source Wherein when a new database is formed, the information about the data structure includes information that can be used to optimize the new database; And  Storing at least a portion of said information about a data structure in a data storage device How to include. The method of claim 41, wherein Creating a data repository without first forming the new database How to include more. The method of claim 41, wherein Forming the new database How to include more. The method of claim 43, Forming the new database includes forming the new database having a structure different from that of the first data source. Way. The method of claim 43, The new database is optimized using the information about the data structure. Way. The method of claim 43, The first data source is a database Way. The method of claim 43, Requesting information from a user to be used, at least in part, when determining the structure of the new database How to include more. The method of claim 47, The requesting step includes displaying a dialog box. Way. The method of claim 47, The requesting step includes displaying a choice list. Way. The method of claim 43, After forming the new database, populating the new database. How to include more. The method of claim 41, wherein The information about the data structure includes an identifier of at least some of the account portions. Way. The method of claim 41, wherein The information about the data structure includes a query stored at the first data source. Way. The method of claim 42, wherein Generating the data repository is performed prior to using a computer to obtain information regarding the data structure of the first data source. Way.