Creating and modifying tables utilizing a database application and a database core that stores user data can be an arbitrary endeavor. Users create tables and once a table is created, it's difficult to change or modify table schema in a way that is intuitive to users and is easy to use. Schema defines the table and schema modification options and/or dialog are so deeply rooted into a database application such that modifying the table requires a higher level of skill and core knowledge of database concepts in order to manipulate the database application. Thus, users who are not familiar with formal database theory, or who do not possess preconceived notions of what database design is, need help in determining and setting data types and other features based on their input data.
Previous database application versions only modify tables when a user is not viewing the data. Thus, a user of a previous version cannot use or operate a table and change the table at the same time. Also, in previous versions, data types of the data entered are guessed only after the user closes the table. And a user is prohibited from making changes to the structure of a table while a database object that depends on the table, such as a form or query, is open. Thus, in previous versions, in order to modify the schema of the table, data objects depending on the table have to be closed so that nothing else is using the table. For instance, when a user tries to modify a table while a dependent report is open, the user may receive an arbitrary notice to close the report and the table.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended as an aid in determining the scope of the claimed subject matter.
Embodiments of the present invention solve the above and other problems by providing methods, systems, and computer-readable mediums for modifying database table definitions. In general, the present invention allows users of a database application to change a table definition while the user is looking at the data. The present invention makes it easier than ever to modify database table definitions by adding new fields to a table or modifying the definition of fields in a table while browsing data. Embodiments of the present invention provide uniquely flexible and easy methods for working with table schema. The present invention includes a user-friendly method of adding a field to a table's schema and improved paste behavior for adding new fields. Some embodiments also include automatic, interactive data type guessing when a user types or pastes chunks of data into a new field or into a column that contains the new field and transparent handling of blocking dependencies from other database objects the user has open.
One embodiment is a method for modifying a table definition of a database table within a database application. The method involves providing a user interface for creating a new field in the database table, receiving data that creates the new field via the user interface while displaying the database table, and modifying schema of the database table to include the new field and the data. The method also involves interpreting a data type of the data as the data is received in the new field. A data type interpreted for a column in the database table that contains the new field is the data type of the data received in the new field. Still further, the method involves handling objects dependent on the database table in a manner unbeknownst to a user of the database table. Thus, the schema is modified while the objects dependent on the database table remain visible to the user.
Another embodiment is a computer program product including a computer-readable medium having control logic stored therein for causing a computer to modify a table definition of a database table within a database application. The control logic includes computer-readable program code for causing the computer to provide a user interface for creating a new field in the database table, receive data that creates the new field via the user interface while displaying the database table, and modify schema of the database table to include the new field and the data.
Still another embodiment is a computer-implemented system for modifying a table definition of a database table within a database application. The system includes a computing apparatus having a processor operative to provide a user interface for creating a new field in the database table, receive data that creates the new field via the user interface while displaying the database table, and modify schema of the database table to include the new field and the data. The processor may also be operative to interpret a data type of the data as the data is received in the new field and handle objects dependent on the database table in a manner unbeknownst to a user of the database table.
These and other features and advantages, which characterize the present invention, will be apparent from a reading of the following detailed description and a review of the associated drawings. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention as claimed.
a are illustrative operational flows performed in interpreting a data type of data received according to illustrative embodiments of the present invention;
As briefly described above, embodiments of the present invention are directed to methods, computer program products, and systems for modifying a table definition of a database table within a database application. These embodiments may be combined, other embodiments may be utilized, and structural changes may be made without departing from the spirit or scope of the present invention. The following detailed description is therefore not to be taken in a limiting sense and the scope of the present invention is defined by the appended claims and their equivalents.
Referring now to the drawings, in which like numerals refer to like elements through the several figures, aspects of the present invention and an exemplary operating environment will be described.
Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
The mass storage device 114 is connected to the CPU 104 through a mass storage controller (not shown) connected to the bus 112. The mass storage device 114 and its associated computer-readable media, provide non-volatile storage for the personal computer 102. Although the description of computer-readable media contained herein refers to a mass storage device, such as a hard disk or CD-ROM drive, it should be appreciated by those skilled in the art that computer-readable media can be any available media that can be accessed by the personal computer 102.
“Computer storage medium” includes volatile and non-volatile, removable and non-removable storage medium implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage medium includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other storage medium which can be used to store the desired information and which can be accessed by a computer.
According to various embodiments of the invention, the personal computer 102 may operate in a networked environment using logical connections to remote computers through a TCP/IP network 118, such as the Internet. The personal computer 102 may connect to the TCP/IP network 118 through a network interface unit 120 connected to the bus 112. It should be appreciated that the network interface unit 120 may also be utilized to connect to other types of networks and remote computer systems. The personal computer 102 may also include an input/output controller 122 for receiving and processing input from a number of devices, including a keyboard or mouse (not shown). Similarly, an input/output controller 122 may provide output to a display screen or unit 123, a printer, or other type of output device.
As mentioned briefly above, a number of program modules and data files may be stored in the mass storage device 114 and RAM 108 of the personal computer 102, including an operating system 116 suitable for controlling the operation of a networked personal computer, such as the WINDOWS operating systems from Microsoft Corporation of Redmond, Wash. The mass storage device 114 and RAM 108 may also store one or more application programs. In particular, the mass storage device 114 and RAM 108 may store the application program suite 117 for providing a variety of functionalities to a user. For instance, the application program 105 may comprise many types of programs such as a word processing application, a spreadsheet application, a desktop publishing application, and the like.
According to an embodiment of the present invention, the database application 115, such as ACCESS from Microsoft Corporation of Redmond, Wash., includes an interactive tool or graphical user interface module (UIM) 107. The UIM 107 is operative to modify a table definition of a database table, such as database tables 128a-128n, while displaying or rendering one or more corresponding datasheets with data, such as datasheets 112a-112n, to a user of the database application 115. The database application 115 may also be associated with the application program suite 117. The application program suite comprises a multiple functionality software application suite for providing functionality from a number of different software applications. An example of such a multiple functionality application suite 117 is OFFICE manufactured by Microsoft Corporation. Other application programs 124 illustrated in
Upon receiving the data 702 that conflicts with a currency or number data type, the UIM 107 renders a notice 704 indicating the entered data does not match the number values in the field or column 701. The UIM 107 also renders options 707 for resolving the conflict, such as entering a new value or converting the entire column or field 701 to text. Additional details regarding interpreting data types will be described below with respect to
At operation 807, the UIM 107 receives data entry for one or more new fields via user typing and/or a paste operation. Next, the routine 800 continues to operation 808 where the UIM 107 interprets a data type of the data received as the data is received based on a first data entry or a paste operation. Additional details regarding interpreting a data type when the data is received is described below with respect to
At operation 810, the UIM 107 handles any blocking dependencies from objects, such as queries and dependent tables. The objects are handled based on their object type and their current view. Previously, dependent objects had to be closed to a user before table modifications could occur. However, in embodiments of the present invention, the UIM 107 handles blocking dependencies such that any handling is transparent to a user viewing the dependent objects and the datasheet view of the table. The UIM 107 temporarily closes dependency references to the database table without removing the objects from the view of a user. Additional details regarding transparently handling blocking dependencies will be described below with respect to
At operation 812, the UIM 107 modifies the schema of the underlying table in accordance with new field data entries. Then, at operation 814, the UIM 107 stores the modifications and continues to operation 815. At operation 815, the UIM 107 reinstates or restores dependency references to the database table that were temporarily closed at operation 810 described above. The routine 800 then returns control to other routines at return operation 817.
At operation 905, the UIM detects whether the data item is potentially a currency value. When the data items could be currency, the routine 800 continues to operation 907. At operation 907 a determination is made as to whether higher precision is needed or whether only one currency symbol (e.g. ‘$’) exist with numbers. For example, when one or more values that appear to be currency values (e.g. $1.23), are followed by a numeric value (e.g. 1.23456789), higher precision is needed because both numbers cannot be accurately represented using a currency data type. Thus in this case, the data type is interpreted as number with loading point double precision (double) instead of currency. Similarly, when one or more values appear to be integers (e.g. 37, 498), but a value cannot be represented as an integer (e.g. 4.5), the data type is interpreted as number (double) instead of number (integer).
Thus, when higher precision is needed or only one currency symbol is present, the routine 808 continues from operation 907 to operation 908 where the UIM 107 sets the data type to number. Because there is only one type of currency symbol mixed in with numbers, the symbol can be removed from the value. Number data types facilitate improved filtering, aggregation, and other features that a text data type would not. When a user desires a currency format can be applied separately to convert the number field to a currency data type. The routine 808 then continues to operation 934 described below.
When at operation 907, higher precision is not needed or multiple symbols or currency types are present, the routine 808 continues from operation 907 to operation 914. At operation 914, the UIM 107 detects whether the number of characters present in a data item is greater than a predetermined threshold, for example 255 characters. When the number of characters is less than the threshold, the routine 808 continues to operation 915 where the UIM 107 sets the data type to text. The routine 808 then continues to operation 934 described below.
When at operation 914, the number of characters is not less than the threshold, the routine 808 continues to operation 917 where the UIM 107 sets the data type to memo. The routine 808 then continues to operation 934 described below.
At operation 905, when no currency symbols are present, the routine 808 continues to operation 920 where the UIM 107 detects whether only numbers are present. When only numbers are present the routine 808 continues to operation 908 described above. When only numbers are not present, the routine 808 continues from operation 920 to operation 922.
At operation 922, the UIM 107 detects whether the data includes date and/or time content. When the data includes date and/or time information the routine 808 continues to operation 924 where the UIM 107 sets the data type to date/time and applies a general date format. The routine 808 then continues to operation 934 described below.
When at operation 922, the UIM 107 detects not only date and/or time information is present, the routine 808 continues to operation 925. At operation 925, the UIM 107 detects whether the data forms a hyperlink. When the data forms a hyperlink, the routine 808 continues to operation 927 where the UIM 107 sets the data type to hyperlink. The routine 808 then continues to operation 934 described below.
When at operation 925, the UIM 107 detects that the data does not form a hyperlink, the routine 808 continues to operation 930. At operation 930, the UIM 107 detects whether data forms a Boolean value, such as yes or no. When the data forms a Boolean value, the routine 808 continues to operation 932 where the UIM 107 sets the data type to Boolean. The routine 808 then continues to operation 934 described below. When at operation 930, the UIM 107 detects that the data does not form a Boolean value, the routine 808 continues to operation 914 described above.
At operation 934, the UIM 107 synthesizes the data types for the current data item with the previous data item if a previous data item is present. Thus, for example if a number (double) data type is detected after an integer data type, the UIM 107 synthesizes the data type to number (double). Next at operation 937, the UIM 107 determines whether more data is present. When more data is present, the routine 808 continues from operation 937 to operation 938, where the UIM 107 gets the next data item. The routine 808 then continues to operation 904 described above.
When more data is not present at operation 937, the routine 808 continues from operation 937 to operation 941. At operation 941, the UIM 107 sets the data type of the column to the synthesized data type. The routine 808 returns control to routine 800, operation 810 at return operation 942.
In another embodiment of the present invention, when data is received in a column that has already been assigned a data type, as illustrated in
Then at operation 954, the UIM 107 detects a data type of the column receiving the data. The routine 900 then continues to operation 957. At operation 957, the UIM 107 detects whether the data type of the data received is compatible with or matches the data type of the column. When the data types are compatible, the routine 900 returns control to routine 800, operation 810 at return operation 965.
At operation 957 when the data types are not compatible, the routine 900 continues to operation 960. At operation 960, the UIM 107 renders or displays a notice of conflicting data types and options for resolving the conflict. The options may include entering another value or converting the data type to text. The routine 900 then continues to operation 963.
At operation 963, the UIM 107 receives and implements the option selected by a user. The routine 900 then returns control to other routines at return operation 965 described above.
Next, at operation 1004, the UIM 107 detects whether there are any other objects utilizing the database table. When no objects are using the table, the routine 810 returns control to routine 800, operation 812 at return operation 1022. When one or more objects are dependent on the table, the routine 810 continues to operation 1007.
At operation 1007, the UIM 107 detects an object type and a view of each object utilizing the database table. It should be appreciated that the object types may include the following: another table having a lookup query to the database table, a query, a form having a record source that depends on the database table, and/or a report. It should also be appreciated that the various object views may include the following: a design view, a datasheet view, a form view, a report view, a print preview view, and/or a chart or pivot view.
Next, the routine 810 continues from operation 1007 to operation 1010. At operation 1010, the UIM 107 tracks a primary key identifier for each row being modified in the database table. Additional details regarding a primary key will be described below with respect to
Referring now to
Referring to
Returning to
Next, based on the object type and view of the dependency object(s), the routine 810 continues from operation 1011 to operations 1012, 1014, 1017, 1018, and/or 1020. Thus, according to Table 1, when the view is set to print preview view and the object type is table, query, report or form, the routine 810 continues from operation 1011 to operation 1018 where the UIM 107 executes according to legend number 2 described above.
Similarly, when the view is set to chart view or pivot view and the object type is table, query, or form, the routine 810 continues from operation 1011 to operation 1020, where the UIM 107 executes according to legend number 3 described above.
Still further, when the view is set to datasheet view and the object type is table, query, or form, or when the view is set to form and the object type is form, the routine 810 continues from operation 1011 to operation 1014 where the UIM 107 executes according to legend number 1 described above.
Also, when the view is set to design and the object type is set to form or report, the routine 810 continues from operation 1011 to operation 1017, where the UIM 107 executes according to legend number 4 described above.
Similarly, when the view is set to report view and the object type is report, the routine 810 continues from operation 1011 to operation 1020 where the UIM 107 executes according to legend number 5 described above except the primary key may not be tracked depending on how the report data is generated.
Next, the routine 810 continues to operation 1021 where the UIM 107 temporarily disengages any dependency reference from the table while maintaining availability or visibility of the dependency object. The routine 810 then continues to return operation 1022 described above.
Based on the foregoing, it should be appreciated that the various embodiments of the invention include methods, systems, and computer-readable mediums for modifying a table definition of a database table within a database application. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended.
Number | Name | Date | Kind |
---|---|---|---|
5121499 | McCaskill et al. | Jun 1992 | A |
5175810 | Young et al. | Dec 1992 | A |
5247611 | Norden-Paul et al. | Sep 1993 | A |
5255356 | Michelman et al. | Oct 1993 | A |
5319777 | Perez | Jun 1994 | A |
5359729 | Yarnell et al. | Oct 1994 | A |
5396587 | Reed et al. | Mar 1995 | A |
5418898 | Zand et al. | May 1995 | A |
5418902 | West et al. | May 1995 | A |
5455853 | Cebulka et al. | Oct 1995 | A |
5471575 | Giansante | Nov 1995 | A |
5510980 | Peters | Apr 1996 | A |
5535324 | Alvarez et al. | Jul 1996 | A |
5553215 | Kaethler | Sep 1996 | A |
5598519 | Narayanan | Jan 1997 | A |
5600584 | Schlafly | Feb 1997 | A |
5604854 | Glassey | Feb 1997 | A |
5615373 | Ho | Mar 1997 | A |
5649192 | Stucky | Jul 1997 | A |
5685001 | Capson et al. | Nov 1997 | A |
5701499 | Capson et al. | Dec 1997 | A |
5708827 | Kaneko et al. | Jan 1998 | A |
5740370 | Battersby et al. | Apr 1998 | A |
5752253 | Geymond et al. | May 1998 | A |
5758337 | Hammond | May 1998 | A |
5768158 | Adler et al. | Jun 1998 | A |
5812983 | Kumagai | Sep 1998 | A |
5819293 | Comer et al. | Oct 1998 | A |
5838965 | Kavanagh et al. | Nov 1998 | A |
5864854 | Boyle | Jan 1999 | A |
5881381 | Yamashita et al. | Mar 1999 | A |
5890174 | Khanna et al. | Mar 1999 | A |
5893920 | Shaheen et al. | Apr 1999 | A |
5913033 | Grout | Jun 1999 | A |
5920725 | Ma et al. | Jul 1999 | A |
5926822 | Garman | Jul 1999 | A |
5944789 | Tzelnic et al. | Aug 1999 | A |
5966716 | Comer et al. | Oct 1999 | A |
5987481 | Michelman et al. | Nov 1999 | A |
6021413 | Vaduvur et al. | Feb 2000 | A |
6055548 | Comer et al. | Apr 2000 | A |
6055549 | Takano | Apr 2000 | A |
6070177 | Kao et al. | May 2000 | A |
6112214 | Graham et al. | Aug 2000 | A |
6119151 | Cantrell et al. | Sep 2000 | A |
6134552 | Fritz et al. | Oct 2000 | A |
6134563 | Clancey et al. | Oct 2000 | A |
6134583 | Herriot | Oct 2000 | A |
6138130 | Adler et al. | Oct 2000 | A |
6151601 | Papierniak et al. | Nov 2000 | A |
6151624 | Teare et al. | Nov 2000 | A |
6216139 | Listou | Apr 2001 | B1 |
6292811 | Clancey et al. | Sep 2001 | B1 |
6334158 | Jenny et al. | Dec 2001 | B1 |
6341291 | Beatley et al. | Jan 2002 | B1 |
6374268 | Testardi | Apr 2002 | B1 |
6477527 | Carey et al. | Nov 2002 | B2 |
6510439 | Rangarajan et al. | Jan 2003 | B1 |
6542933 | Durst, Jr. et al. | Apr 2003 | B1 |
6567822 | Cudahy et al. | May 2003 | B1 |
6631519 | Nicholson et al. | Oct 2003 | B1 |
6640234 | Coffen et al. | Oct 2003 | B1 |
6694321 | Berno | Feb 2004 | B1 |
6785704 | McCanne | Aug 2004 | B1 |
6820088 | Hind et al. | Nov 2004 | B1 |
7062502 | Kesler | Jun 2006 | B1 |
7139768 | Janzig et al. | Nov 2006 | B1 |
7174327 | Chau et al. | Feb 2007 | B2 |
20020049764 | Boothby et al. | Apr 2002 | A1 |
20020052769 | Navani et al. | May 2002 | A1 |
20020063734 | Khalfay et al. | May 2002 | A1 |
20020087729 | Edgar | Jul 2002 | A1 |
20030046366 | Pardikar et al. | Mar 2003 | A1 |
20030145224 | Bailey | Jul 2003 | A1 |
20030154191 | Fish et al. | Aug 2003 | A1 |
20030154197 | Millet et al. | Aug 2003 | A1 |
20030158947 | Bloch et al. | Aug 2003 | A1 |
20030159089 | DiJoseph | Aug 2003 | A1 |
20030225758 | Yamasaki | Dec 2003 | A1 |
20040001106 | Deutscher et al. | Jan 2004 | A1 |
20040039743 | Maleport et al. | Feb 2004 | A1 |
20040103365 | Cox | May 2004 | A1 |
20040133652 | Miloushev et al. | Jul 2004 | A1 |
20040138815 | Li et al. | Jul 2004 | A1 |
20040172424 | Edelstein et al. | Sep 2004 | A1 |
20040193969 | Nemoto et al. | Sep 2004 | A1 |
20040236777 | Pardikar et al. | Nov 2004 | A1 |
20050034064 | Meyers et al. | Feb 2005 | A1 |
20050069361 | Wang et al. | Mar 2005 | A1 |
20050080823 | Collins | Apr 2005 | A1 |
20050091253 | Cragun et al. | Apr 2005 | A1 |
20050172261 | Yuknewicz et al. | Aug 2005 | A1 |
20050187897 | Pawar et al. | Aug 2005 | A1 |
20050228990 | Kato et al. | Oct 2005 | A1 |
20060004815 | Murata et al. | Jan 2006 | A1 |
20060020586 | Prompt et al. | Jan 2006 | A1 |
20060155705 | Kamper et al. | Jul 2006 | A1 |
20060168325 | Wood et al. | Jul 2006 | A1 |
20060168557 | Agrawal et al. | Jul 2006 | A1 |
20060200499 | Bhatia et al. | Sep 2006 | A1 |
20060242189 | Leetaru et al. | Oct 2006 | A1 |
20060259506 | Kim | Nov 2006 | A1 |
20070038702 | Taylor et al. | Feb 2007 | A1 |
20070198657 | Saliba et al. | Aug 2007 | A1 |
Number | Date | Country |
---|---|---|
1452981 | Sep 2004 | EP |
WO 0060484 | Oct 2000 | WO |
Number | Date | Country | |
---|---|---|---|
20070005630 A1 | Jan 2007 | US |