Abstract:
A global information network forms completion data processing system uses data stored in a database to automatically fill out data fields of the various and multiple forms displayed on the WEB browsers of users who are engaged in commerce, dealing with governmental agencies, or otherwise attempting to complete transactions over the global information network. The data processing system retrieves tagged information previously entered and stored in a database, and automatically inserts the data in similarly tagged uncompleted fields of any number and variety of forms. The fully completed forms are then transmitted to the parties requesting the information and are stored for later retrieval, updating and printing by the user.

Description:
FIELD OF THE INVENTION 
     The present invention is an improvement in the field of data processing over the global information network and more specifically it is a data processing system for automatically completing forms displayed on users web browsers. 
     BACKGROUND OF THE INVENTION 
     Many users of the global information network are often required to fill out multiple and varied forms to do business with a variety of companies doing electronic commerce, or contact companies or regulatory agencies for a variety of reasons. For example, a user applying for a credit card may have to complete a form with the same information he or she just filled in on a different form used to order some goods or services from a different company. Those users applying for jobs and completing application papers or security clearance papers may find themselves completing various forms over and over again using the same information, but having to reenter it because the format of the forms are different. 
     Electronic commerce over the global information network relies heavily on forms and in some cases, up to several dozen forms may have to be filled out. Such forms may include initial customer set up checklists, customer credit forms, and follow-up forms, and even return e-mails to be sent back to the customer. Regulatory agencies also rely heavily on many different forms for applications or information gathering. 
     Historically such forms were typically filled out manually and placed in a file folder. Little information was available on-line or in a data processing system. All follow-up action on a particular case required access to this file. Locating the file was often a problem leading to time lost and wasted in searching for the file. Additionally, a manual file system also resulted in incomplete files due to forms not being placed in the file, or forms improperly or incompletely filled out. 
     More recent prior art systems are focused mainly on internal systems. U.S. Pat. No. 5,640,577 discloses a data processing system including automated forms generation that uses data displayed at a predetermined position on a data terminal display screen, and a data processing function selector, to automatically retrieve a pre-established form stored in a data processing system. In one embodiment, the form includes a number of uncompleted fields. The data processing system retrieves at least one datum from at least one data field displayed on the screen, and automatically inserts the data in a predetermined uncompleted field of the form. The partially or fully completed form is then stored for later retrieval, updating and printing by the data processing system. 
     These types of systems are now common on intranet based processing within companies, but they are complicated systems generally requiring personnel with significant technical expertise to install, create the forms, and set up the mapping of the information to the forms. Also, a customer or applicant first approaching the company with his or her personal information must start by completing the companies set of forms. The process must be repeated over and over again each time that the person goes to a new company. Such a method is extremely time consuming, further ties up the host computer resources, and often results in numerous data entry errors. This further results in delays in processing the customer cases and an accompanying tendency to act on incomplete or improperly compiled information. 
     It is therefore the object of this invention to supply multiple users of the global information network with a convenient method of automatically completing multiple forms for multiple companies or regulatory agencies, by filing out the information once on any form presented on the user&#39;s web browser. It is also an object of this invention to allow the user the opportunity to update their individual information automatically when they are completing a new form on their web browser. It is a further object of this invention to allow multiple companies or regulatory agencies who do electronic commerce or other applications over the global information network a simple method that can be implemented by non technical staff to transfer their forms to automatically filling electronic forms. And also to offer multiple users a convenient way of entering information into all the data fields on their many forms automatically. 
     SUMMARY OF THE INVENTION 
     The present invention has been made to solve the problems described above. It is a global information network forms completion data processing system that uses data stored in a database to automatically fill out data fields of the various and multiple forms displayed on the web browsers of multiple users who are engaged in commerce with companies, dealing with governmental agencies, or otherwise attempting to complete transactions over the global information network. Once a company, or regulatory agency using this system registers its forms the data processing system retrieves tagged information previously entered by the user and stored in a database, and automatically inserts the data in similarly tagged uncompleted fields of any number and variety of registered forms. The fully completed forms are then transmitted to the parties requesting the information and are also stored for later retrieval, updating and printing by the user. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     Other objects, features and advantages of the present invention will become apparent from the detailed description of the invention that follows, when considered in light of the accompanying drawings in which: 
     FIG. 1 is a flow diagram of the forms mapping data flow. 
     FIG. 2 is a diagram of the usage data flow. 
     FIG. 3 is a diagram of the tables and relationships between them residing in the relational database. 
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
     The present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which preferred embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout. 
     In the preferred embodiment the data processing system is a tool designed to eliminate incomplete and incorrect information associated with filling out forms by potential candidates or employees of a company. Of course those skilled in the art will recognize this system can be used by a variety of entities using forms to collect information for any number of reasons. A form is any document that requests specific information from one party for the purpose of communicating with another party. The preferred embodiment provides an electronic method of capturing that information, replacing the traditional paper form. The tool validates that all required information has been entered and that fields that require a specific format are correct. 
     The tool consists of two separate modules. The first module is the Mapping Application, used to identify the forms, their fields, and the clients subscribing to each form, and then map that information into a relational database. The relational database used in the preferred embodiment is Sybase, Inc.&#39;s Adaptive Server Enterprise database. The second module is the Web Form Filler that uses a web server that allows potential candidates or employees of a company to fill out the forms electronically. The server used in the preferred embodiment is Sybase, Inc.&#39;s Jaguar Component Transaction Server. 
     Referring now to FIG. 1 a reader skilled in the art can follow the flow of information in the Mapping Application as a company registers its forms in the system. An External Entity (1), the company, submits form information to the Mapping Application over the Global Information Network or Local Network to the Form Registrar (2) a computer processor. The Form Registrar (2) gives the form a unique identifier and submits that information to the Form Database (3). The External Entity (1) also submits an HTML or a scanned PDF version of the form that is also given the unique identifier and is stored in the Form Database (3). The form template is also sent to the Form Field Identifier (4) that is also a computer processor. The Form Field Identifier (4) parces out and identifies each data field on the submitted form and sends that information to the Form Fields (7) database. Meanwhile the Common Industry Mapper (5), another computer processor, pulls information about the industry group associated with the form being registered from the Form Database (3) and maps that information to the Industry Common Fields (8) database. 
     Next a Form Field Matcher (6) pulls information regarding all the data fields from the Form Fields (7) database and common industry fields from the Industry Common Fields (8) database and sends information in the form of unmatched fields back to the External Entity (1) to compare with common fields. The External Entity (1) verifies common fields and submits the information back to the Form Field Matcher (6) as matched fields. After verification The Form Field Matcher then sorts the common fields (those that were matched) from the uncommon fields (those left unmatched), sending the common fields to the Identified Common Form Fields (9) database, and the uncommon fields to the Identified Unique Form Fields (10) database for storage and retrieval when needed later by a user filling out the registered form. The External Entity (1) can then process the information regarding registration of its form and store the information for later retrieval in its Data Store (11). This same process is then repeated by the External Entity (1) for the rest of the forms that it wishes to register. 
     Referring now to FIG. 2 one skilled in the art can follow the flow of information in the data processing system when being accessed by a user to fill out a form. A Web User (12), company candidate or employee, requests a form over the Global Information Network or a Local Network and enters information on his or her display. The information is then transferred over the network to the Form Parcer (13), which is a network server. The Form Parcer (13) submits the request for the form and inputted data to the Form Database (3). The Form Database (3), a relational database further described below, supplies form field information with additional common information to the Form Builder (14). The Form Builder (14) is a computer processor that gathers all the previously stored data associated with the user&#39;s request from the relational database and separates PDF data from Non PDF data The Non PDF data is stored in a copy of the completed form at the Completed Form (18) storage. The rest of the data, which is all PDF data, makes up the FDF File (15), and is sent to the PDF Merger (7). 
     The PDF Merger (7), a computer that uses PDF Merge by Digital Apps, Adobe PDF fill software, or other PDF merge software well known to those skilled in the art, completes the form by merging the FDF File (15) with an Empty Adobe PDF File (16), which is the stored form template that was previously identified with the form being filed out. The filled out PDF file is then stored in the Completed Form (18) storage where it can be viewed at a later time. The full file consisting of the completed PDF form and the Non PDF data is also sent to the Form Send (19) server. 
     The Form Send (19) server sends the file back over the network to an External Entity (1) that has need of the information submitted by the Web User (10). The External Entity (1) processes the information and stores the information for later retrieval in its Data Store (11). 
     As mentioned above this system operates with a relational database application. There are six main components within the relational database application. They are Industries, Common Tags, Form, Form Tags, Packages, and Clients. The following section describes each of the components. 
     An Industry is an area of business that satisfies a particular need or service. For the purpose of the preferred embodiment, an Industry is an area of business that requires specific information unique to that industry. An Industry may also require information common to all industries such as the applicant&#39;s name, social security number and address. 
     A Common Tag is any single piece of information that may be requested for a particular industry. Common Tags identify information that may appear on more than one form, such as applicant&#39;s first name, but will only be stored once. If the applicant edits the field on one form, information is changed for all form&#39;s fields the Common Tag is associated with. 
     A Form within the preferred embodiment is the abstract representation of a paper form in the physical world. It is a collection of questions an individual must answer. Examples of forms are an employment application, a W2, and a benefits enrollment form. A Form may consist of form fields and other Forms. An example of a Form contained within a Form may be an employment application, which will contain the previous employment form. The previous employment form may be filled out several times for an individual depending on the number of previous employment&#39;s they have had. In the preferred embodiment the Form is stored as an Adobe Acrobat PDF document and are filled in using PDF Merge software by Digital Apps, or other merging software well know by those skilled in the art. 
     A Form Tag is any single piece of information that will be requested of the web user when they select its related form. Each tag created on the form&#39;s Adobe Acrobat document is related to one Form Tag. A Form Tag however may be a single piece of information or a concatenation of any number of Form Tags. An example of a concatenated Form Tag may be a telephone number where the telephone number is made up of the area code and the telephone number. The web user would be requested to fill in their area code and telephone number in two separate fields. The Adobe Acrobat form would contain only a single tag for telephone number, consisting of the concatenation of the two fields. 
     A Package is a collection of related Forms. A Package must have at least one Form. A Form can belong to any number of different Packages. A Client can subscribe to one or more Packages. Any number of Clients can subscribe to a Package. This allows Forms and Packages to be set up only once but used by multiple Clients. 
     A Client represents the company an individual is applying to or is currently employed with. Client information is not maintained within the database application, only the relationship between Clients and Packages. 
     These components make up the relational database where the information is stored for use by the Mapping Application and the Web Form Filler. Below is a list of the Tables in the relational database, and the relationships between them. The database software creates each form specific table. The workings of the following listings will be obvious when read by someone skilled in the art of relational database theory and design. In these Tables the following definitions apply: 
     Column List: A list of database table fields that information is stored in. 
     Index List: An index provides faster access to the data. This is the list of indexes per table 
     Reference to List: Defines pointers to another table by key identifier. 
     Reference by List: Tables that have a pointer to this table&#39;s unique key identifier. 
     Name: Name of column. 
     Code: An internal identifier used by the database software. 
     Type: The type of data, i.e. numeric, character, etc., and length of data. 
     Primary Key: The unique identifier for each row of table&#39;s data. 
     Foreign Key: Used to identify the primary key of the reference to table. 
     Index Code: An internal identifier used by the database software. 
     Column Code: An internal identifier used by the database software. 
     P: Primary key for this column. 
     M: Mandatory, defines if the column must be defined &#34;yes&#34; or can contain null (unknown) values. 
     F: Foreign Key on this column. 
     A: Alternate key, another way to identify the data. 
     U: Unique, all values stored in this column must be unique within the entire table. 
     C: Cluster, the physical order that the data in a table is stored. In this case it is sorted (clustered) in the same order as the index. 
     
         ______________________________________Table applicant______________________________________Column ListName       Code        Type     P     M______________________________________applicant.sub.-- id      applicant.sub.-- id                  int      Yes   Yesclient.sub.-- id      client.sub.-- id                  int      No    Nofrom.sub.-- EBQ      from.sub.-- EBQ                  char(10) No    Yes______________________________________Reference to ListPrimary Key   Reference to  Foreign Key______________________________________client.sub.-- id         client        client.sub.-- id______________________________________Reference by ListReferenced by    Primary Key Foreign Key______________________________________industry.sub.-- data.sub.-- example2            applicant.sub.-- id                        applicant.sub.-- idform.sub.-- data applicant.sub.-- id                        applicant.sub.-- idindustry.sub.-- data.sub.-- example            applicant.sub.-- id                        applicant.sub.-- id______________________________________ 
    
     
         ______________________________________Table client______________________________________Column ListName       Code       Type     P      M______________________________________client.sub.-- id      client.sub.-- id                 int      Yes    Yes______________________________________Index ListIndex Code    P      F     A    U    C    Column Code                                         Sort______________________________________PK.sub.-- CLIENT    Yes    No    No   Yes  Yes  client.sub.-- id                                         ASC______________________________________Reference by ListReferenced by   Primary Key Foreign Key______________________________________client.sub.-- subscription           client.sub.-- id                       client.sub.-- idapplicant       client.sub.-- id                       client.sub.-- id______________________________________ 
    
     
         ______________________________________Table client.sub.-- subscription______________________________________Column ListName         Code         Type    P    M______________________________________subject.sub.-- area.sub.-- id        subject.sub.-- area.sub.-- id                     int     No   Noclient.sub.-- id        client.sub.-- id                     int     No   No______________________________________Reference to ListPrimary Key    Reference to                      Foreign Key______________________________________subject.sub.-- area.sub.-- id          subject.sub.-- area                      subject.sub.-- area.sub.-- idclient.sub.-- id          client      client.sub.-- id______________________________________ 
    
     
         ______________________________________Table common.sub.-- tags______________________________________Column ListName       Code         Type     P     M______________________________________tag.sub.-- id      tag.sub.-- id                   int      Yes   Yesindustry.sub.-- key      industry.sub.-- key                   int      No    Yesdescription      description  char(40) No    Yesstored.sub.-- length      stored.sub.-- length                   int      No    Yesstored.sub.-- data.sub.-- type      stored.sub.-- data.sub.-- type                   char(10) No    Yescolumn.sub.-- name      column.sub.-- name                   char(30) No    Yes______________________________________Index List                                   ColumnIndex Code   P      F     A   U    C    Code  Sort______________________________________PK.sub.-- COMMON.sub.-- TAGS        Yes    No    No  Yes  Yes  tag.sub.-- id                                         ASC______________________________________Reference to ListPrimary Key    Reference to                      Foreign Key______________________________________industry.sub.-- key          industry    industry.sub.-- key______________________________________Reference by ListReferenced by  Primary Key  Foreign Key______________________________________form.sub.-- tags          tag.sub.-- id                       tag.sub.-- id______________________________________ 
    
     
         __________________________________________________________________________Table concatinetion.sub.--__________________________________________________________________________Column ListName        Code      Type                     P  M__________________________________________________________________________Database.sub.-- tag.sub.-- id       database.sub.-- tag.sub.-- id                 int Yes                        YesScreen.sub.-- tag.sub.-- id       screen.sub.-- tag.sub.-- id                 int Yes                        YesStyle       style     int No YesCat.sub.-- order       cat.sub.-- order                 int No YesSeparater   seperater char(1)                     No YesTrailing.sub.-- blanks       trailing.sub.-- blanks                 char(1)                     No YesSub.sub.-- field.sub.-- location       sub.sub.-- field.sub.-- location                 int No Yes__________________________________________________________________________Index ListIndex Code P  F A U  C  Column Code                           Sort__________________________________________________________________________PK.sub.-- CONCATINATION      Yes         No           No             Yes                Yes                   database.sub.-- tag.sub.-- id                           ASC                   screen.sub.-- tag.sub.-- id                           ASC__________________________________________________________________________Reference to ListPrimary Key   Reference to                  Foreign Key__________________________________________________________________________Form.sub.-- tag.sub.-- id         form.sub.-- tags                  database.sub.-- tag.sub.-- idForm.sub.-- tag.sub.-- id         form.sub.-- tags                  screen.sub.-- tag.sub.-- id__________________________________________________________________________ 
    
     
         ______________________________________Table form______________________________________Column ListName       Code         Type      P    M______________________________________Form.sub.-- id      form.sub.-- id                   int       Yes  YesDescription      description  char(80)  No   YesActive.sub.-- date      active.sub.-- date                   datetime  No   YesInactive.sub.-- date      inactive.sub.-- date                   datetime  No   YesUnedited.sub.-- pdf      unedited.sub.-- pdf                   image     No   NoTable.sub.-- generated      table.sub.-- generated                   char(1)   No   Yes______________________________________Index ListIndex Code   P      F      A    U    C    Column Code                                         Sort______________________________________PK.sub.-- FORM   Yes    No     No   Yes  Yes  form.sub.-- id                                         ASC______________________________________Reference by ListReferenced by   Primary Key                      Foreign Key______________________________________form.sub.-- data           form.sub.-- id                      form.sub.-- idform.sub.-- relationship           form.sub.-- id                      ancestor.sub.-- form.sub.-- idform.sub.-- relationship           form.sub.-- id                      decendant.sub.-- form.sub.-- idform.sub.-- tags           form.sub.-- id                      form.sub.-- idsubject.sub.-- area.sub.-- form.sub.-- list           form.sub.-- id                      form.sub.-- id______________________________________ 
    
     
         __________________________________________________________________________Table form.sub.-- data__________________________________________________________________________Column ListName      Code     Type  P  M__________________________________________________________________________form.sub.-- data.sub.-- id     form.sub.-- data id              int   Yes                       Yesform.sub.-- id     form.sub.-- id              int   No Noapplicant.sub.-- id     applicant.sub.-- id              int   No Noform.sub.-- PDF     form.sub.-- PDF              image No Yesdate.sub.-- last.sub.-- entered     date.sub.-- last.sub.-- entered              datetime                    No Yesupdateable     updateable              char(1)                    No Yesversion.sub.-- number     version.sub.-- number              smallint                    No Yes__________________________________________________________________________Index ListIndex Code     P  F A U  C  Column Code                         Sort__________________________________________________________________________PK.sub.-- FORM.sub.-- DATA     Yes        No          No            Yes               Yes                  form.sub.-- data.sub.-- id                         ASC__________________________________________________________________________Reference to ListPrimary Key   Reference to                  Foreign Key__________________________________________________________________________form.sub.-- id         form     form.sub.-- idapplicant.sub.-- id         applicant                  applicant.sub.-- id__________________________________________________________________________Reference by ListReferenced by  Primary Key                   Foreign Key__________________________________________________________________________industy.sub.-- data.sub.-- example2          form.sub.-- data.sub.-- id                   form.sub.-- data.sub.-- id__________________________________________________________________________ 
    
     
         __________________________________________________________________________Table form.sub.-- relationship__________________________________________________________________________Column ListName         Code       Type P    M__________________________________________________________________________ancestor.sub.-- form.sub.-- id        ancestor.sub.-- form.sub.-- id                   int  Yes  Yesdecendant.sub.-- form.sub.-- id        decendant.sub.-- form.sub.-- id                   int  Yes  Yesform.sub.-- level        form.sub.-- level                   int  No   Yesform.sub.-- order        form.sub.-- order                   int  No   Yes__________________________________________________________________________Index ListIndex Code    P  F A U  C  Column Code                               Sort__________________________________________________________________________PK.sub.-- FORM.sub.-- RELATIONSHIP         Yes            No              No                Yes                   Yes                      ancestor.sub.-- form.sub.-- id                               ASC                      decendant.sub.-- form.sub.-- id                               ASC__________________________________________________________________________Reference to ListPrimary Key    Reference to                    Foreign Key__________________________________________________________________________form.sub.-- id form      ancestor.sub.-- form.sub.-- idform.sub.-- id form      decendant.sub.-- form.sub.-- id__________________________________________________________________________ 
    
     
         __________________________________________________________________________Table form.sub.-- specific.sub.-- data.sub.-- ex__________________________________________________________________________Column ListName        Code        Type P  M__________________________________________________________________________industry.sub.-- data.sub.-- id       industry.sub.-- data.sub.-- id                   int  Yes                           Yesform.sub.-- data.sub.-- id       form.sub.-- data.sub.-- id                   int  No Yesapplicant.sub.-- id       applicant.sub.-- id                   int  No Yesdate.sub.-- entered       date.sub.-- entered                   datetime                        No Noname.sub.-- long       name.sub.-- long                   char(43)                        No Nofirst.sub.-- name       first.sub.-- name                   char(20)                        No Nolast.sub.-- name       last.sub.-- name                   char(20)                        No Nomiddle.sub.-- initial       middle.sub.-- initial                   char(1)                        No Nossn         ssn         char(10)                        No Nobirthdate   birthdate   datetime                        No Nomothers.sub.-- maden.sub.-- name       mothers.sub.-- maden.sub.-- name                   char(20)                        No Noaddress1    address1    char(40)                        No Noaddress2    address2    char(40)                        No Nocity        city        char(20)                        No Nostate.sub.-- provence       state.sub.-- provence                   char(3)                        No Nopostal.sub.-- code       postal.sub.-- code                   char(10)                        No Noform.sub.-- question1       form.sub.-- question1                   char(80)                        No Noform.sub.-- question2       form.sub.-- question2                   char(80)                        No Noform.sub.-- question3       form.sub.-- question3                   char(80)                        No No__________________________________________________________________________Index ListIndex Code  P  F A U  C  Column Code                            Sort__________________________________________________________________________PK.sub.-- INDUSTRY.sub.-- DATA2       Yes          No            No              Yes                 Yes                    industry.sub.-- data.sub.-- id                            ASC__________________________________________________________________________Reference to ListPrimary Key    Reference to                    Foreign Key__________________________________________________________________________form.sub.-- data.sub.-- id          form.sub.-- data                    form.sub.-- data.sub.-- idapplicant.sub.-- id          applicant applicant.sub.-- id__________________________________________________________________________ 
    
     
         __________________________________________________________________________Table form.sub.-- tags__________________________________________________________________________Column ListName       Code     Type P   M__________________________________________________________________________form.sub.-- tag.sub.-- id      form.sub.-- tag.sub.-- id               int  Yes Yesform.sub.-- id      form.sub.-- id               int  No  Yestag.sub.-- id      tag.sub.-- id               int  No  Noactual.sub.-- form.sub.-- text      actual.sub.-- form.sub.-- text               char(60)                    No  Yesdescription      description               char(80)                    No  Yesvalidation.sub.-- script      validation.sub.-- script               char(40)                    No  Yestag.sub.-- name      tag.sub.-- name               char(40)                    No  Yestag.sub.-- data.sub.-- type      tag.sub.-- data.sub.-- type               char(3)                    No  Yesrequired.sub.-- flag      required.sub.-- flag               char(1)                    No  Yesconcatinated.sub.-- flag      concatinated.sub.-- flag               char(1)                    No  Yesform.sub.-- tag.sub.-- type      form.sub.-- tag.sub.-- type               char(8)                    No  Nochecked.sub.-- flag      checked.sub.-- flag               char(1)                    No  Noform.sub.-- tag.sub.-- align      form.sub.-- tag.sub.-- align               char(8)                    No  Nomaxlength  maxlength               int  No  Nosize       size     int  No  No__________________________________________________________________________Index ListIndex Code    P  F A U  C  Column Code                        Sort__________________________________________________________________________PK.sub.-- FORM.sub.-- TAGS    Yes       No         No           Yes              Yes                 form.sub.-- tag.sub.-- id                        ASC__________________________________________________________________________Reference to ListPrimary Key Reference to                  Foreign Key__________________________________________________________________________form.sub.-- id       form       form.sub.-- idtag.sub.-- id       common.sub.-- tags                  tag.sub.-- id__________________________________________________________________________Reference by ListReferenced by        Primary Key                 Foreign Key__________________________________________________________________________concatinetion        form.sub.-- tag.sub.-- id                 database.sub.-- tag.sub.-- idconcatinetion        form.sub.-- tag.sub.-- id                 screen.sub.-- tag.sub.-- idform.sub.-- tags.sub.-- radio        form.sub.-- tag.sub.-- id                 form.sub.-- tag.sub.-- id__________________________________________________________________________ 
    
     
         __________________________________________________________________________Table form.sub.-- tags.sub.-- radio__________________________________________________________________________Column ListName      Code     Type P    M__________________________________________________________________________form.sub.-- tag.sub.-- id     form.sub.-- tag.sub.-- id              int  Yes  Yesform.sub.-- radio.sub.-- id     form.sub.-- radio.sub.-- id              int  Yes  Yesdb.sub.-- value     db.sub.-- value              char(20)                   No   Yesact.sub.-- radio.sub.-- text     act.sub.-- radio.sub.-- text              char(20)                   No   Yes__________________________________________________________________________Index ListIndex Code P  F A U  C  Column Code                          Sort__________________________________________________________________________form.sub.-- tags.sub.-- 7680057671      Yes         No           No             Yes                Yes                   form.sub.-- tag.sub.-- id                          ASC                   form.sub.-- radio.sub.-- id                          ASC__________________________________________________________________________Reference to ListPrimary Key   Reference to                   Foreign Key__________________________________________________________________________form.sub.-- tag.sub.-- id         form.sub.-- tags                   form.sub.-- tag.sub.-- id__________________________________________________________________________ 
    
     
         ______________________________________Table industry______________________________________Column ListName        Code        Type      P     M______________________________________industry.sub.-- key       industry.sub.-- key                   int       Yes   Yesname        name        char(40)  No    Yesdescription description char(255) No    Yestable.sub.-- creation       table.sub.-- creation                   char(1)   No    Yestable.sub.-- name       table.sub.-- name                   char(60)  No    Yestable.sub.-- created       table.sub.-- created                   char(1)   No    Yes______________________________________Index ListIndex Code     P      F     A   U    C    Column Code                                         Sort______________________________________PK.sub.-- INDUSTRY     Yes    No    No  Yes  Yes  industry.sub.-- key                                         ASC______________________________________Reference by ListReferenced by Primary Key  Foreign Key______________________________________common.sub.-- tags         industry.sub.-- key                      industry.sub.-- key______________________________________ 
    
     
         __________________________________________________________________________Table industry.sub.-- data.sub.-- example__________________________________________________________________________Column ListName        Code        Type P  M__________________________________________________________________________industry.sub.-- data.sub.-- id       industry.sub.-- data.sub.-- id                   int  Yes                           Yesapplicant.sub.-- id       applicant.sub.-- id                   int  No Yesdate.sub.-- entered       date.sub.-- entered                   datetime                        No Noname.sub.-- long       name.sub.-- long                   char(43)                        No Nofirst.sub.-- name       first.sub.-- name                   char(20)                        No Nolast.sub.-- name       last.sub.-- name                   char(20)                        No Nomiddle.sub.-- initial       middle.sub.-- initial                   char(1)                        No Nossn         ssn         char(10)                        No Nobirthdate   birthdate   datetime                        No Nomothers.sub.-- maden.sub.-- name       mothers.sub.-- maden.sub.-- name                   char(20)                        No Noaddress1    address1    char(40)                        No Noaddress2    address2    char(40)                        No Nocity        city        char(20)                        No Nostate.sub.-- provence       state.sub.-- provence                   char(3)                        No Nopostal.sub.-- code       postal.sub.-- code                   char(10)                        No No__________________________________________________________________________Index ListIndex Code  P  F A U  C  Column Code                            Sort__________________________________________________________________________PK.sub.-- INDUSTRY.sub.-- DATA       Yes          No            No              Yes                 Yes                    industry.sub.-- data.sub.-- id                            ASC__________________________________________________________________________Reference to ListPrimary Key   Reference to                     Foreign Key__________________________________________________________________________applicant.sub.-- id         applicant   applicant.sub.-- id__________________________________________________________________________ 
    
     
         __________________________________________________________________________Table subject.sub.-- area__________________________________________________________________________Column ListName       Code     Type  P   M__________________________________________________________________________subject.sub.-- area.sub.-- id      subject.sub.-- area.sub.-- id               int   Yes Yesname       name     char(40)                     No  Yesdescription      description               char(255)                     No  Yeseffective.sub.-- date      effective.sub.-- date               T.sub.-- date                     No  Yes__________________________________________________________________________Index ListIndex Code P  F A U  C  Column Code                           Sort__________________________________________________________________________PK.sub.-- SUBJECT.sub.-- AREA      Yes         No           No             Yes                Yes                   subject.sub.-- area.sub.-- id                           ASC__________________________________________________________________________Reference by ListReferenced by  Primary Key                    Foreign Key__________________________________________________________________________client.sub.-- subscription          subject.sub.-- area.sub.-- id                    subject.sub.-- area.sub.-- idsubject.sub.-- area.sub.-- form.sub.-- list          subject.sub.-- area.sub.-- id                    subject.sub.-- area.sub.-- id__________________________________________________________________________ 
    
     
         __________________________________________________________________________Table subject.sub.-- area.sub.-- form.sub.-- list__________________________________________________________________________Column ListName         Code       Type  P    M__________________________________________________________________________subject.sub.-- area.sub.-- id        subject.sub.-- area.sub.-- id                   int   Yes  Yesform.sub.-- id        form.sub.-- id                   int   Yes  Yesform.sub.-- order        form.sub.-- order                   int   No   Yesmandatory    mandatory  char(1)                         No   Yesrepeatable   repeatable int   No   Yes__________________________________________________________________________Index ListIndex Code       P  F A U  C  Column Code                                 Sort__________________________________________________________________________PK.sub.-- SUBJECT.sub.-- AREA.sub.-- FORM.sub.-- LIST            Yes               No                 No                   Yes                      Yes                         subject.sub.-- area.sub.-- id                                 ASC                         form.sub.-- id                                 ASC__________________________________________________________________________Reference to ListPrimary Key      Reference to                       Foreign Key__________________________________________________________________________subject.sub.-- area.sub.-- id            subject.sub.-- area                       subject.sub.-- area.sub.-- idform.sub.-- id   form       form.sub.-- id__________________________________________________________________________ 
    
     The relationships between these tables are also shown in graphical form on FIG. 3. 
     Many modifications and other embodiments of the invention will come to the mind of one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention is not to be limited to the specific embodiments disclosed, and that modifications and embodiments are intended to be included within the scope of the dependent claims.