Simplified interface for relational database access using open database connectivity

• US 6,065,002 A
• Filed: 10/31/1996
• Issued: 05/16/2000
• Est. Priority Date: 10/31/1996
• Status: Expired due to Term

• Current Assignee: Ellucian Company L.P.
• Original Assignee: Systems and Computer Technology Corporation
• Inventors: Knotts, James Brian, Marsilio, Robert Eric, Clouser, Michael Fleming, Bailey, Robert Lynn
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): RONES, CHARLES
• Application Number:
  US08/741,705
• Time in Patent Office: 1,293 Days
• Field of Search: 707/4, 707/103, 345/326
• US Class Current: 1/1
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation

Abstract

A user interface is provided to a relational database to provide simplified data access for users. A user input/output device interacts with an application tool accessible via a computer. A template accessible to the application tool via an API or native interface provides a selection of attributes corresponding to a particular category. The attributes specify information obtainable from data stored in the relational database and are selectable using the application tool. The template is responsive to attributes selected using the application tool, for retrieving data from the relational database and forwarding the data to the application tool via the API or native interface. The template is independent of the application tool, thereby enabling the user interface to access information from the relational database using any of a plurality of different application tools. Functions are also provided for use in calculating complex attributes from data contained in the database, where the complex attribute is not itself contained in the database.

Claims

1. An open database connectivity (ODBC) compliant system for accessing data from a relational database, comprising:

user input/output device for interacting with an ODBC compliant application tool accessible via a computer;

an ODBC interface;

an ODBC compliant template for simplifying access to complex data stored in said relational database, said template being accessible to said application tool via said ODBC interface for enabling user selection of attributes corresponding to a particular category, said attributes specifying information obtainable from data stored in said relational database and being selectable using said application tool;

said ODBC compliant template being responsive to selected attributes received from said application tool via said ODBC interface, for retrieving data from said relational database and forwarding said data to said application tool via said ODBC interface for use in generating an output;

wherein;

said ODBC compliant template is independent of said application tool, thereby enabling a user to access information from said relational database using any one of a plurality of different application tools; and

said template (i) directly accesses attributes selected via said application tool when the selected attributes are stored in the database or (ii) when the selected attributes are not stored in the database, enables complex attributes selected via said application tool to be calculated via selectively executable algorithms by obtaining data from said database that is required by said algorithms.

2. An ODBC compliant system in accordance with claim 1 comprising a plurality of different ODBC compliant templates, each providing a set of attributes corresponding to a different category, said attributes specifying information obtainable from data stored in said relational database for their associated category.

3. An ODBC compliant system in accordance with claim 2 wherein said ODBC interface comprises an application program interface (API) for allowing said application tool, said templates, and said database to communicate.

4. An ODBC compliant system in accordance with claim 1 comprising a plurality of different ODBC compliant templates, each providing a set of attributes corresponding to a different category, said attributes specifying information obtainable from data stored in said relational database for their associated category.

5. An ODBC compliant system in accordance with claim 1 wherein said application tool includes at least one of a report writer, statistical analysis tool, spreadsheet and desktop tool that is ODBC compliant.

6. An ODBC compliant system in accordance with claim 1 wherein said ODBC interface comprises an application program interface (API) for allowing said application tool, said templates, and said database to communicate.

7. An ODBC compliant system in accordance with claim 1 wherein said template requires a user to designate, via said application tool, information for at least one mandatory condition.

8. An ODBC compliant system in accordance with claim 1 wherein said application tool is provided with direct access to said database in addition to access to said database via said template.

9. An ODBC compliant system in accordance with claim 8 wherein:

said application tool and said template are ODBC compliant; and

data obtained by said application tool directly from said database and data obtained by said application tool via said template are able to be combined due to the ODBC compliant nature of said tool and template for use in generating said output.

10. An ODBC compliant system in accordance with claim 1 further comprising means for enabling a user to specify properties for customizing said template.

11. An ODBC compliant system in accordance with claim 10 wherein said properties are specified using said application tool.

12. An ODBC compliant system in accordance with claim 1 wherein said template comprises:

a meta layer that dynamically converts data from said relational database into a simplified conceptual format.

13. An ODBC compliant system in accordance with claim 12 wherein said simplified conceptual format is a format that avoids the complexity of relationships within the structure of said relational database.