Patent Publication Number: US-5893098-A

Title: System and method for obtaining and collating survey information from a plurality of computer users

Description:
This application is a divisional of copending application Ser. No. PCT/AU95/00615 filed on Sep. 14, 1995. 
    
    
     This application is a divisional of copending application Ser. No. PCT/AU95/00615 filed on Sep. 14, 1995. 
     FIELD OF THE INVENTION 
     The present invention relates to a system and method for obtaining and collating information from a plurality of computer users. More particularly, but not exclusively, the invention relates to a method and system for asking questions of computer users having access to electronic mail, and to a method and system for collating their responses and presenting them in a database. 
     BACKGROUND OF THE INVENTION 
     In recent years, developments in communication systems and computer technology have enabled communication between computers over vast distances utilising communications networks. Employing electronic mail, it is possible for a user of a personal computer (or any other type of computer) with access to a modem or other network communications interface, to communicate with any number of users of remote computers e.g., via the internet. Distance is no barrier. Further, in small or large companies electronic mail networks are often used to connect user terminals to enable communication in-house between users. 
     The possibility of communication with any number of users having access to electronic mail opens up vast information gathering potential. 
     To obtain and process such large amounts of information, however, presents a number of problems. Using electronic mail for a user of a computer may ask a question or questions of a relatively large number of remote users, by addressing mail including a question or questions to those users. 
     The task of processing responses to the question or questions becomes extremely difficult. Where a large number of users provide responses, the task can be almost impossible. This difficultly will be aggravated where a large number of questions are asked. The amount of information to process can be staggering and the user who asked the questions may be faced with the onerous task of sorting through a large amount of mail, item by item, to extract and collate the information he requires. Where a large amount of information is required from a large number of people, it is impractical for one person to deal with. 
     Consider the example of opinion polls, whether for marketing, political or other purposes. Presently, large numbers of field operators are required to gather numerous responses from members of the public. Once those responses have been gathered, hundreds and even thousands of man-hours are required to process the responses to extract the required information and present it in a form which allows for analysis. Thousands of questionaries may need processing, each with many Questions and responses. It should also be noted that the time taken to gather and process the responses can mean that the information finally revealed from the opinion poll has lost it&#39;s relevance or at least become less relevant. Consider a political opinion poll, where peoples opinions may be varying from day to day, significantly enough to affect the election result. An opinion poll which takes two or three days to process will be out of date and irrelevant by the time the results are available for publication. 
     There are really two major problems with presently available &#34;surveying&#34;. Firstly, there is the problem of how does a person ask the questions of all the people he wishes to ask the questions of, without expending many man hours or employing a number of people as field operators? This problem is somewhat alleviated by the existence of systems such as electronic mail, which enable a person to select a number of people to send a single document to. There is the problem here, however, that no convenient means exists of asking a series of complex, linked questions. For example, a persons answer to a particular question may determine whether or not a subsequent question is relevant to that person. If the person is asked whether they are taking leave from employment that year to go on holiday, and answer no, there is no point in asking them where they are going on holiday. Electronic mail communication systems do not deal with that problem. 
     Even though electronic mail may be used to somewhat alleviate the problem of getting a question to a number of people, such systems do nothing to alleviate the problems associated with processing the answers. There is no alternative but for the person asking the question to sort through return mail item by item to, first of all, identify which mail is in response to his questions, and, then, to collate and process the responses to enable a meaningful analysis. 
     These problems are not limited to large surveys, such as political opinion polls. Even quite small surveys can present problems of time management. For example, imagine if a director of a company with fifty or so employees wishes to plan staff leave for the year. He has to ask all his employees when they would like to take leave. He may also wish to know where they want to go. He can do this by sending out a memo and awaiting the results, or perhaps even sending out a memo on intra office computer mail and awaiting the results. He still has to process all the results. Processing results, analysing them and planning the leave even of only fifty people can be quite time consuming, particularly for a person with many other responsibilities who does not really have the time to spend on such a task. Further, the managing director may wish to ask many different types of questions of his staff on a on-going day-to-day basis. His only option for processing the responses is to do it himself, item by item, or, if he has not got time (as is usually the case) to employ somebody to do it. 
     SUMMARY OF THE INVENTION 
     In a preferred embodiment, the present invention advantageously provides a way of asking a question of any number of users, preferably via electronic mail or an equivalent communications media, and automatically receiving, identifying and processing responses to the question. 
     From a first aspect, the present invention provides A system for obtaining information from a plurality of computer users: 
     comprising a processing apparatus including an input means via which a survey author may input data, and a survey authoring means enabling construction of a survey questionnaire document including at least one question formulated from data input by the survey author; 
     transmission means for transmitting the survey questionnaire document to a plurality of respondent users; and 
     a processing apparatus including a collating means arranged to receive transmissions from the transmission means, to identify response documents which include responses to the at least one question from the plurality of respondent users and to load a database in accordance with the responses. 
     A &#34;survey author&#34; is any person who wishes to use the survey document authoring means to construct a survey questionnaire document. 
     The transmission means is preferably electronic mail. Please note that the terminology electronic mail is not only used in a narrow sense, but used in a more general sense, to mean any way of communicating between computer users utilising telecommunications media (telephone, optical fibre, satellite, etc.) which enables a user or group of users or a location e.g., a &#34;relative&#34; location such as a &#34;bulletin board&#34; to be designated by an address, preferably a unique address. The transmission means may even include transmission of floppy disks including the response document, by ordinary mail, although this is not preferable. 
     Where electronic mail is employed, the collator means is preferably arranged to monitor all electronic mail being received by the processing apparatus in which the collator means is included, to sort the electronic mail to identify response documents. Electronic mail not including a response document is not processed any further by the collation means. Where a response document is identified, further processing takes place. Preferably, the further processing includes locating the database which is to receive the responses to the survey document, and loading the database in accordance with the responses. 
     In at least preferred embodiments, the apparatus and method of the present invention advantageously enables the user of a processing apparatus such as a computer to prepare a survey document asking for information on any subject he desires, utilising at least one question or any number of questions determined by the user, to transmit the survey document to any number of remote processing apparatus, preferably by electronic mail, to receive and automatically collate response documents containing or specifying responses to the survey document provided by users of the remote processing apparatus to which the survey document is transmitted, and loading the database with answers, so that the answers are all conveniently presented in a database for subsequent analysis. 
     The invention preferably provides the ability to gather information very easily and quickly over vast distances and to automatically present the information in an already-collated and format. It can be used for any number of information gathering applications. 
     The information obtained by embodiments of this invention is preferably &#34;fresh&#34;. It can be obtained very quickly and is therefore more likely to be relevant than information obtained by prior art methods, such as opinion polling. Because the information is automatically processed and presented in a database, there is no need to undertake the laborious job of individually processing each response document. An immense amount of time can be saved. Because of the automatic collation, a single survey author may poll thousands of respondent users, their responses being processed for him automatically almost as soon as they arrive. It can be considered akin to the survey author simultaneously having a &#34;conversation&#34; with thousands of people. Instead of the responses being a jumble of noise, as it would in a real life conversation with such a crowd, the user receives the information presented in an immediately understandable format of his choice. 
     The database used may be any type of computer data storage arrangement. It may be a relational database or series of databases of the type presently known. The database preferably includes a plurality of fields for receiving answers dictated by the responses. Each database field for an answer is preferably uniquely identified by a column label, which may relate to the question asked, and a &#34;row&#34; label which relates to the identity of the respondent user. The terms &#34;columns&#34; and &#34;rows&#34; are not used in any limited sense to indicate that all the databases are physically matrixes (although they can be represented that way), but to indicate that each answer field has a unique identifier. The row label is preferably the electronic mail name and address of the respondent user. One or more &#34;columns&#34; in the database may be required to contain the row electronic mail address. 
     Note that the possibility exists of allowing for more than one answer by the same user to the same survey document. For example, a respondent user may be asked to answer the survey document every week. In that case, the system may be arranged to override the previous weeks data field values or add a further row, including the latest response and identifying it by date and time of response as well as electronic mail name and address. 
     The data base field values may be derived from the response provided by the respondent user or may actually be the response provided by the respondent user, e.g., where the response is text information. 
     Once the database has been loaded with values, then the information can be manipulated in any way the user requires, utilising all the database facilities. For example, graphical plots may be made of responses. 
     A particular advantage of using E-Mail is that it is possible to store the address of respondent users in the database, for later use. It would then, for example, be possible to mail back further questions to persons giving a particular response to one or more questions in a previous survey document. For example, if a particular survey question was &#34;Do you like chocolate&#34;, and half the respondents said yes and the other half said no, it would be possible to prepare a further survey document asking; &#34;Would you like to have a free sample of our new chocolate bar brand X&#34;, and only mail it to the respondent users who said &#34;yes&#34; to liking chocolate. Using the properties of databases the second survey document could be prepared and transmitted very quickly, merely by instructing the processing apparatus that the survey document is only to go to those people that said yes to the &#34;Do you like chocolate?&#34; question. This illustrates the &#34;conversational&#34; advantages of at least preferred embodiments of this invention, as discussed previously. It is possible to obtain responses from people in a very short time period and use the information from those responses to ask further questions. 
     The system therefore preferably has the ability to mail to respondents of previous surveys, to facilitate this &#34;conversational&#34; style of communication. Note that the process of &#34;conversation&#34; may be particularly important when the analysed data shows a trend that the Survey Author did not expect and did therefore not include any questions to cover this eventuality. He can produce further survey documents to send to the respondents including those questions that he did not include in the first place. Conversation is further facilitated by the ability to choose which respondents to mail to, may be depending upon their responses to previous questions, combined with the ability to store electronic mail name and address lists of respondents. 
     The database is preferably created automatically by the survey authoring means, preferably when the survey document has been completed, and, more preferably, immediately before transmission of the survey document. It is not generally necessary for the user to input any data specifically to prepare the database, although a facility is preferably available to enable the user to choose labels for database columns and/or rows. 
     As the survey author constructs the survey document, the survey preparation means is preferably arranged to allow labels for database columns to be inserted. If the user does not wish to insert any labels himself, the survey document preparation means is preferably arranged to select the headings itself, i.e., by default. 
     The database is preferably constructed as a matrix, having at least one question column and a plurality of user rows, the rows and columns specifying a plurality of database answer fields for receipt of answers (being derived from the respondent users responses) to the at least one question, each row being associated with a particular respondent user who may receive or has received the survey document and may provide or has provided an answer document (response document). The question column is associated with the at least one question asked. It will be appreciated, as discussed above that the matrix format is preferred, but it will also be appreciated that the invention extends to cover any type of database structure. 
     The survey questionnaire document or a subset thereof may be stored to enable re-transmission of the survey document at a later stage, as a reminder should any of the pre-selected users not have provided a response document. The database is also preferably constructed just prior to transmission. Where the respondent user identities are known the entire database may be constructed (pre-populated). 
     It will be appreciated that the option does exist of constructing a database as answer documents are received and processed, e.g., a particular user row will only be added when an answer document is processed. This embodiment may have applications where, for example, the survey document is posted on a &#34;bulletin board&#34; for use by any persons who wish to answer the survey. Each row or row label will therefore only be added as responses come in and are processed by the collation means. The response document preferably includes an identifier identifying the database survey it belongs to, so that the collation means can load the appropriate database with the response and construct a further row label. 
     The use of electronic mail enables selection of any type of user, group of users, posting on a bulletin board, etc. 
     By &#34;user&#34; is meant any natural person or group of persons, company or generally an &#34;identity&#34; who may be specified by the survey author. 
     The survey document may be saved on a respondent users system this enables the remote user (respondent user) to send responses back to the collator when and as often as desired. This could be useful in any circumstances where data is collected on a regular basis. For example, recording telephone sales inquiries. 
     The survey document may include any number of questions and may also include branched-to questions linked to another question or questions such that the branched-to question or questions will only be required to be answered by a respondent user if the respondent (remote user) user gives a predetermined answer to the question or series of questions to which the branched-to question is linked. A survey document may include a string of questions linked to each other and the branched-to question or questions may be asked if the remote user has given one or more predetermined answers to the string of questions and to the question to which the branched-to question is linked. In a preferred embodiment, the survey document is presented to the respondent user as a plurality of screens (where there are a plurality of questions), each screen asking, generally, one question. A screen presenting a branched-to question will not be presented by the display to the remote user unless he makes one or more predetermined answers to a previous question or questions. Whether a branched-to question is presented may also depend on whether another or other questions have been presented or will be presented to the remote user (respondent user). In other words, if the respondent users answers have meant that he has &#34;bypassed&#34; a question or questions, then a particular branched-to question may be presented. Note that it is also possible to ask a number of questions on a single screen and whether a particular question is presented may depend on his answer or combination of answers to any one or more of these questions. The survey document in this preferred embodiment is &#34;dynamic&#34;, in the sense that it will only present questions to a respondent user if the respondent user has made a predetermined answer or answers to a linked question or questions. The survey document will guide the respondent user on a path through the document which is determined by the respondent users answers. Questions which are not relevant to the respondent user, as determined by his answers to other questions, will never be asked of the respondent user. This has the advantage that it is not necessary for the respondent user to wade through a series of displayed questions to find the ones that are relevant to him. He will be automatically guided through the document. It saves time. 
     The survey authoring means preferably includes a branch control means which enables construction of a complex linked survey document structure on the basis of data input by the survey author. The branch control means includes branch control operator commands which are selectable by the survey author to govern the link structure. These are a tools which the survey author can use to construct a complex document with many pathways through it. 
     Preferably, the step of preparing the survey document includes specifying an allowable answer or a plurality of allowable answers to the at least one question, so that remote users of may specify at least one of the allowable answers, when processing the survey document on their computer(s). Preferably, a database field value is specified for each allowable answer. In a preferred embodiment, when the answer document is processed, the database field value is entered in the appropriate database field. 
     The field value may be comprised of numeric or alphanumeric characters, may be any desired symbol or symbols. In a preferred embodiment, the specified field value for a particular question may be generated automatically from components of the question itself, components of the allowable answer, or may be an automatically generated default. 
     The allowable answers in some cases may be text to be inserted by the respondent user. In these cases, a length for the allowable text may be specified by the survey author. The database field value will be whatever text the respondent user inputs, within the allowable field length. This allows for anything from simple answers to more complicated text answers. 
     Where a question or questions is not asked of a particular user, i.e., it may have been bypassed because the users responses to other questions in the survey document meant that it was not appropriate for him to be asked that question or questions (see above) then, preferably, a &#34;never seen&#34; value is entered in the appropriate database field on collation. 
     The person accessing the database can therefore see at a glance whether or not a particular user actually &#34;saw&#34; a particular question. The never-seen value may include any choice of character or group of characters and may be specified by the survey author or as a default by the survey document preparation means. 
     The step of preparing the plurality of allowable answers may include preparing a grid, having rows and columns providing a matrix of cells for receiving the allowable answers. A title head is preferably prepared for each row and column in the matrix. 
     In a preferred embodiment, there are three types of grids which may be applied. An option buttons grid, a numeric field grid and a check box grid. 
     For an option buttons grid only one question column is generally required in the database even though there may be a plurality of cells in the grid for receiving the allowable answers. Preferably, the field values associated with each allowable answer are taken from components of the row and/or column heading for each particular cell. Option button grids may also be provided including sub-groups of option buttons each requiring an answer. In this case, there will be as many question columns in the database as there are groups of option buttons requiring an answer. The groups are preferably in rows and columns. 
     For numeric field grids and check box grids, in the preferred embodiment a question column in the database is required for each cell of the grid. The headings of these question columns may preferably be formed from components of the row and/or column head of the grid. 
     Preferably, the step of preparing the Survey Document further includes the step of scanning the Survey Document when it has been completed by the survey author and identifying any errors in the question structure, utilising a scan test means included in the processing apparatus including the survey authoring means. Generally, each question in the Survey Document must come from at least one previous question and lead to at least one further question, apart from the first and last questions in the Survey Document which will come from the start of the document (N.B., the first question will be designated by the author of the document. In fact, in the preferred embodiment, it is open to the author to formulate the questions first and then designate their sequence in the structure of the document separately) and lead to &#34;finish&#34;, respectively. In a complex document including branched-from and branched-to questions there will be a number of different &#34;pathways&#34; through the Survey Document. It will be appreciated that the structure can be extremely complex. It is quite possible that during preparation of the Survey Document, the local user (the survey author) will make an error in preparation which will lead to one or more of the pathways being incomplete or broken, i.e., a question exists (other than the first question) which does not come from any other question (an &#34;orphan&#34;) or which does not lead from all the questions it is supposed to lead from, and questions may exist which do not lead to any other question (&#34;cul-de-sacs&#34;) or do not lead to all the questions they are supposed to lead to. Any such errors should be identified before the Survey Document is transmitted. This is preferably done by applying a scan test function, which scans through all the pathways in the document to identify errors, particularly of the &#34;orphan&#34; or &#34;cul-de-sac&#34; type, although it may identify other &#34;mechanical&#34; errors of this type which may lead to breakdown of pathway in the Survey Document. The scan test means applying the scan test function will also test for missing, duplicate and illegal database names (e.g., the database name not allowed by the particular database which is being constructed, e.g., in DOS only eight characters are allowed for a database name). 
     The scan test function preferably also provides a display listing of all the variable information in the Survey Document, variable information generally being any item in the document that the local user may exercise a choice in selecting, for example, &#34;Goto&#39;s&#34;, whether the question is branched to or not, database field titles, etc., but does not display, in general, any textual information from the question content of the Survey Document. The listing enables the local user to check that the mechanical structure of the document (the pathways leading through the Survey Document) is correct, by visually checking the listing. Further, in one embodiment, the items in which errors have been identified are indicated in the listing, preferably by highlighting these particular items. By clicking on any of the items on his screen the local user will automatically be taken to the actual item. It is therefore possible for him to easily be able to check the document and correct any errors indicated. 
     In the preferred embodiment, the steps of preparation of survey questionnaire document, transmission, processing of the survey document by a respondent user (remote user) return of the survey document to the collation means and collator, operate as follows: 
     1. A survey master document is originally constructed and includes operator commands for controlling the display of the respondent users computer to display questions, and, in response to the remote users input, to display selected ones of the questions depending upon the linkage structure of the document. It also includes a return E-Mail address for the collation means. E-Mail addresses of respondent users are inserted prior to transmission. The database is constructed from instructions input by the survey author and/or defaults. The survey questionnaire document (preferably a subset of the master) is transmitted and at the same time saved so that reminders can be transmitted if required (note the survey document is preferably transmitted as a &#34;subset&#34; SVQ, of the originally prepared master, sum, and it is the SVQ which is stored). In one preferred embodiment, the survey document is transmitted with respondent control means, used to control the respondents terminal to run the survey document. In an alternative embodiment, a respondent control means is pre-loaded on the respondents computer, and is arranged to control the respondents terminal to process a survey document when one is received. 
     At this time the database is preferably constructed. 
     2. The respondent users terminal is controlled from commands in the survey document and the respondent control means to process the survey document and produce a response document which includes responses based on data input by the respondent user. The response document is automatically transmitted back to the collation means address on completion of a response by the respondent user. The survey response document may include a database construction means which enables construction of the database. This is useful where a disaster has occurred and the database has &#34;crashed&#34;, for some reason. It may also be useful where the collator has moved location and does not have access to the database or does not know the databases address. 
     3. The collation means monitors electronic mail at the processing address including the collation means and identifies response documents. It checks the identifier including the response document to identify the database it belongs to. It then locates the appropriate database and commences to process the survey document to load the database with answers determined by the respondent users responses. Note that the collation means and survey author may be on separate processing apparatus. The survey author may also be a different person from the person who is accessing the database to obtain the information. For example, the survey author may be a pollster employee, and the person accessing the information may be the pollster. The survey author can put together the surveys on the basis of instructions provided by the pollster as to what type of information he wants. All the survey author needs to know about the collation means is the collation means electronic mail address. The database may be loaded on the same processing apparatus as the collation means or on any other processing apparatus. 
     The collation means may be collating any number of surveys. It may collate surveys for any number of survey authors. 
     The response document may be encrypted for security reasons. 
     Preferably, the collation means is also arranged to identify electronic mail addresses of respondent users from response documents are attached messages and to load the database with the electronic mail addresses. These electronic mail addresses can then be easily accessed for future surveys. 
     Where a range of databases are used, a great deal of information can be obtained over time about a particular respondent user who has received a number of surveys. 
     All &#34;documents&#34; are preferably in &#34;data processing representation&#34; form. In other words, they are in an electronic or other form able to be manipulated by a data processing apparatus, e.g., a computer, and, in some aspects, to control a computer. By &#34;computer&#34; is meant any processing apparatus which is able to manipulate data. This includes computers which use other means apart from electrical signals to process data. 
     From a second aspect, the present invention provides a processing apparatus for enabling construction of a survey questionnaire document, comprising an input means via which a survey author may input data, a survey authoring means enabling construction of a survey questionnaire document including at least one question formulated from data input by the survey author and a location address of a processing apparatus including a collator means arranged to collate response documents produced by respondent users processing the survey questionnaire document. 
     The survey authoring means may include any or all of the features of the survey authoring means discussed above, for preparing a survey document with any or all of the features of the survey document discussed above. 
     From a third aspect, the present invention provides a survey questionnaire document structure, the document being employable by digital document processing systems to gather information from a plurality of respondent computer users, the document structure including: 
     a location address for a collation means for receiving response documents to the survey questionnaire document from respondent users; and 
     instructions enabling control of a computer to display one or more questions to be answered by a user. 
     From a fourth aspect the present invention provides a processing apparatus for collating response documents received from a plurality of respondent users in response to their receiving a survey questionnaire document from a processing apparatus, including a collator means arranged to monitor incoming transmissions from a transmission means and identify response documents, which include responses and to load a database in accordance with the responses. 
     From a fifth aspect the present invention provides a processing apparatus for receiving and processing survey questionnaire documents produced by an apparatus, including a respondent control means arranged to process the survey questionnaire document in accordance with data input by a respondent user, to produce a response document including a response to the at least one question. 
     From a sixth aspect the present invention provides a computer-readable memory including a set of instructions for enabling a processing apparatus to enable construction of a survey questionnaire document, the document being employed to gather information from a plurality of respondent users, the instructions enabling the computer to operate as a survey authoring means enabling construction of a survey document including at least one question formulated from data input to the computer by a survey author, and a location address for a collation means for receiving and collating response documents respondent users in response to their processing the survey questionnaire document. 
     From a seventh aspect the present invention provides a computer-readable memory storing a set of instructions that can be used to direct a processing apparatus to operate as a collator means, for collating response documents in response to a survey questionnaire document produced by a processing apparatus, the instructions operating the processing apparatus to monitor incoming transmissions for response documents, and to load a database in accordance with responses. 
     From an eighth aspect the present invention provides a computer-readable memory storing a set of commands that can be used to direct a processing apparatus to process a survey questionnaire document produced by the apparatus, to produce a response document including a response to the at least one question, to be transmitted on a location for a collation means for collating responses. 
     From a ninth aspect the present invention provides a method of obtaining information from a plurality of computer users, comprising operating a processing apparatus including an input means via which a survey author may input data, to construct a survey questionnaire document including at least one question formulated from data input by the survey author, transmitting the survey document to a plurality of respondent users, and controlling a processing apparatus to carry out a collation operation including the steps of receiving transmissions from respondent users, identifying response documents including responses from the plurality of respondent users, and loading a database in accordance with the responses. 
     The tenth aspect of the present invention provides a method of controlling a processing apparatus to construct a survey questionnaire document for obtaining information from a plurality of respondent users, the method comprising the steps of: 
     controlling the processing apparatus to construct a survey questionnaire document including at least one question formulated from data input to the processing apparatus by a survey author; and 
     to include a location address of a processing means for collating responses to the survey from respondent users to load a database in accordance with the responses. 
     The eleventh aspect of the present invention provides a method of collating response documents prepared by respondent users in response to a survey document in accordance with claims 67 or 68, the method comprising the steps of: 
     controlling a processing apparatus to monitor incoming transmissions to the processing apparatus and identify response documents to the survey, and to process the response documents to load a database in accordance with the responses to the at least one question. 
     The thirteenth aspect of the present invention provides a method of controlling a processing apparatus to process a survey questionnaire document produced, to produce a response document formulated from data input by a respondent user, the method comprising the steps of: 
     controlling the processing apparatus to display the at least one question for input of a response by the respondent user; and 
     controlling the respondents computer to prepare a response document for transmission to the collating processor. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     Features and advantages of the present invention will become apparent from the following description of an embodiment thereof, by way of example only, with reference to the accompanying drawings, in which: 
     FIG. 1 is a schematic block diagram of a system in accordance with an embodiment of the present invention incorporating apparatus in accordance with an embodiment of the present invention; 
     FIGS. 2 through 11e show samples of video display screens showing information presented during various stages of preparation of a survey document and answer document (response document), such as may be presented by a display means of a processing apparatus in accordance with an embodiment of the present invention; 
     FIG. 12 illustrates a number of displays which may be presented by a display means of an apparatus in accordance with an embodiment of the present invention, illustrating operation of a collation means in accordance with an embodiment of the present invention; 
     FIG. 13 is a functional diagram of operation of an embodiment of the present invention; 
     FIG. 14 is a schematic representation of a database document which may be prepared in accordance with an embodiment of the present invention; 
     FIG. 15 is an illustration showing the various menu options available to a Survey Author in accordance with a preferred embodiment of the present invention; and 
     FIG. 16 graphically illustrates available setting options for the structure of the survey document of the preferred embodiment, and their operation. 
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
     The following terminology is used interchangeably in this document for specifying the same thing. 
     Response document=answer document. 
     Author=local user. 
     Respondent or respondent user=remote user. 
     Survey authoring means=survey document preparation means. 
     Local processing apparatus=processing apparatus including survey authoring means. 
     Remote processing apparatus=respondent users processing apparatus or computer. 
     Response document=answer document. 
     Responses=answers. 
     In FIG. 1, reference numeral 1 illustrates a is local processing apparatus (a processing apparatus including the survey document preparation means) in the form of a personal computer (PC), comprising a data processing means 2, an input means 3, 4, comprising a keyboard 3 and mouse 4, and a video display unit 5. The local processing means 1 is connected by a communications system 6 to a plurality of remote processing apparatus (a respondent users processing apparatus), each indicated by blocks 7 through 12. It will be appreciated that the local processing apparatus 1 may be connected to any number of remote processing apparatus by any type of communication system 6. Blocks 7 through 12 are given as examples only. Note that the communications system 6 is an illustration only. Preferably, communications is via E-Mail (electronic mail). E-Mail can employ telephones, satellites, optical fibres, etc. All that is required for a user to be connected to E-Mail is that he have an E-Mail address. The E-Mail user may log onto any computer terminal and receive mail. 
     The local processing apparatus 1 includes a survey document preparation means to enable preparation of a survey document containing at least one question and preparation of a database document having at least one database answer field for receiving answers to the at least one question, and a collation means for monitoring incoming E-Mail to identify response documents produced from processing of a survey document, to locate the database relating to the particular survey, and to process the response document to load the at least one database answer field with the answer. 
     Each of the remote processing apparatus are programmed with respondent control means to enable a respondent user to process a received survey document and produce an answer document (response document) from the processing, including responses (answers) formulated from data input by the user of the remote processing apparatus. 
     In a preferred embodiment, the survey document (&#34;survey&#34;) can be prepared and launched using Windows™ with access to mail. To prepare the survey document, in a preferred embodiment a Survey Authoring (SA) module is utilised. The following is a description of preparation of a survey document using a Survey Authoring module in accordance with an embodiment of the present invention. Throughout the description representations of examples of video display unit screen displays produced by this embodiment of the present invention will be referred to, as in FIGS. 2 through 11, to illustrate operation of the invention. 
     After launching the Survey Author Module from Window Program Manager the user of the local processing apparatus (Item 1. FIG. 1.), the author (&#34;local user&#34;), will see the Survey Author Module screen featuring a Menu Bar and Tool Bar. FIG. 4. Also, on launching, the Survey Author Module automatically creates a new survey document. In order to continue authoring this new survey document the author (local user) will need to create the first question. To do this he will choose the QUESTION/NEW QUESTION menu option (FIG. 5). The author (local user) will now be presented with the first blank question box (a frame section on the screen) (FIG. 2). This question box contains the standard NEXT and PREVIOUS buttons as well as an area for question text. 
     As the new question box appears, menu options for a range of question types for the author (local user) to choose from are enabled by the menu system. These types are: 
     Option Button--With a series of Option Buttons the software will accept only one selection by the eventual respondent (remote user). It is like a multiple choice question. The author (local user) will need to make this menu selection for each option button he requires in the current question box. 
     Check Box--A check box enables the eventual respondent (remote user) to enter a &#34;check&#34; (a cross &#34;X&#34; mark signifying a yes or true status) in each check box placed in the question box by the Survey Author (local user). 
     Numeric Field--Same as Check Box except that the respondent (remote user) will enter numbers instead of &#34;checks&#34;. 
     Text Field--Same as numeric field except that the respondent (remote user) will enter any alpha numeric characters rather than numbers. 
     Option Buttons Grid--Grids in general are the same as the first three possible question types mentioned above. The difference is that they are arranged in a grid format. Therefore the author (local user) needs to specify the number of items and the arrangement of those items within the question box. For example: he may specify 12 buttons and an arrangement of 3×4, 4×3, 2×6 or ×2. 
     Check Box Grid--The same as the Option Buttons Grid except that it behaves like a series of Check Boxes. An example of a Grid Check box is given in FIG. 6. 
     Numeric Field Grid--The same as the Option Buttons Grid except that it behaves like a series of Numeric Fields. 
     The question format may include any combination of the above, e.g., a combination of an option buttons grid and a check box grid: 
     FIGS. 11a through 11b illustrate, respectively, means which show dialogue boxes for: 
     1. one option button properties (FIG. 11b) for specifying properties of option buttons. 
     2. Numeric field properties, for specifying properties for a numeric field (FIG. 11c). 
     3. A text field properties dialogue box for specifying properties for a text field (FIG. 11d). 
     4. A label properties dialogue box (FIG. 11e) for specifying &#34;label&#34; for a text field. 
     Displays for option buttons grid, check box grid and numeric field grid are not shown. The requirements for such a display, however, are apparent from the previous and following description on how the display looks is generally a matter for taste of the software engineer and the requirements of the system interface. 
     To construct the survey document, the survey author will need to specify the following: 
     a). Question title (optional); 
     b). Question text; 
     c). Option, check, numeric or alpha label text or any combination thereof; 
     d). Where to GO TO after this question (optional). This would be inserted where the author wishes to link the question to another--see later; 
     e). Alter any database column names (optional); 
     f). Select or alter default on selected database field values (optional); and 
     g). Select or alter default on never seen field values (optional). 
     The author (local user) may specify any one of the above types of question. Lets say the author (local user) wishes to use three &#34;Option Buttons&#34; because he wants to give the respondents (remote users) three possible options to choose from for a specified question. To do this the author (local user) could use their mouse (Item 4. FIG. 1.) to select ITEM/OPTION BUTTON from (see &#34;ITEM&#34; menu, FIG. 15) the menu bar. They would need to do this twice. The first click will cause display of two option buttons. The second will cause display of a third option button. Alternatively the author (local user) could use their mouse to click twice on a &#34;Option Button&#34; Icon on the Tool Bar. Once the author (local user) has finished one of these two actions the frame work of his first question is complete. 
     This first question contains three main features (see FIG. 7): 
     1. Two buttons at the bottom of the screen marked &#34;Next&#34; and &#34;Previous&#34;. 
     2. Three equally spaced &#34;Option Buttons&#34; with &#34;Option Button Text 01&#34;, &#34;Option Button Text 02&#34;, &#34;Option Button Text 03&#34; printed next to them. 
     3. A &#34;Question Text&#34; area towards the top of the dialogue box. 
     The author (local user) is now required to edit the variables for this question box. To do this the author (local user) double clicks on any clear space within the question box. The Question Properties dialogue box will appear on the screen containing the following variables 
     Question Text--This is the area that the author (local user) enters the question that he wants the respondents (remote users) to answer. To enter the &#34;Option Button Text 01&#34;, &#34;Option Button Text 02&#34;, &#34;Option Button Text 03&#34; printed next to them. 
     3. A &#34;Question Text&#34; area towards the top of the dialogue box. 
     The author (local user) is now required to edit the variables for this question box. To do this the author (local user) double clicks on any clear space within the question box. The Question Properties dialogue box (FIGS. 11f and 11g) will appear on the screen containing the following variables 
     Question Text--This is the area that the author (local user) enters the question that he wants the respondents (remote users) to answer. To enter the question text the author (local user) needs to select with his mouse the words &#34;Question Text&#34; and then over type it with the new text. 
     In this example the author (local user) wishes to obtain information from respondents (remote users) as to what leave they will be taking between May and July. The respondents (remote users) may all belong to the same company, for example, and the author (local user) wishes to plan company leave. The author (local user) enters the following question text: 
     &#34;Will you be taking leave from work between May 1, 1994 and Jul. 1, 1994?&#34;. 
     Question Title--These titles are used as reference to their particular question. These references are used in question selection menus, for selecting a current question to edit, and to nominate the branching of the questions (see later). 
     The system generates a default &#34;Question No. 001&#34; where the number part increments for each new question box. The titles may be edited but must be a unique reference within the survey document. In this example the author (local user) will change the Question Title to &#34;LEAVE&#34;. 
     The next step is to enter the relevant defaults for each of the three Option Buttons. To do this the author (local user) simply points at the first Option Button and double clicks with the mouse. The Option Button Properties dialogue box will appear. The main features of this dialogue box are: 
     Option Text--This is where the author (local user) will specify the text that corresponds to that particular option. In the question text the author (local user) asked about staff leave. He should now nominate the text for one of the options that the respondents(remote users) will be able to choose from. 
     For Example: &#34;Yes I will be taking leave during this period&#34;. 
     Database Field Name--This is the name of the column in the database to be prepared in accordance with this embodiment, that will contain answers to this question (the &#34;database column heading&#34;). The column heading may be prepared on the basis of data input by the author (local user) specifically for the column heading. In a preferred embodiment, a default column heading is inserted should the author (local user) not wish to input his own. More preferably, the default may be automatically prepared from components of the question text. This is particularly useful for the check box grid and numeric field grid type questions. Each check box grid or numeric field grid comprises a matrix of rows and columns, each row and column having a header title. Each point (cell) designated by the row and column in the grid matrix is a point where a respondent (remote user) will enter, selectively, an answer. In a preferred embodiment, a database column heading is automatically prepared from components of the row and/or column heading of the check box grid or numeric field grid matrix. In this example this field need only be filled in once as there is only the one Database Column associated with this question. The author (local user) will name the Database Column Heading as &#34;LEAVE&#34;. The default will be the same as the question title. 
     Branched-To Question--This is where the author (local user)enters the next question that this option would take the respondent (remote user) to if the option were selected. Obviously the author (local user)is not able to nominate the next question at this point because he is currently working on the first and only question. However, the author (local user) can nominate one of three special branching destinations. Any of these destinations, {FINISH}, {NEXT} and {NONE} can be used for just this particular question option, or they can be set as the default for this survey document or the entire system. Specifying {FINISH} will mean that the respondent (remote user) will go straight to the Finish Question Box at the end of the survey document. 
     The {NEXT} destination will automatically branch to the next question the author (local user) generates. 
     The {NONE} destination will become a &#34;cul-de-sac&#34;. In other words the question will lead nowhere. When testing the survey document (see later) it will be indicated to the author (local user) that a question exists which is an orphan or a cul-de-sac and the author (local user) will be able to make appropriate corrections. In this example the Option Button text says &#34;Yes I will be taking leave during this period&#34;, and the author (local user) may therefore require additional information so he would want this option to branch to another question. In this example there is only one other question so the author (local user) can select {NEXT} even though the question has not been generated yet. (In an alternative embodiment branching control instructions may be included--see later). 
     On Selection Database Field Value--This is where the author (local user) specifies the entry he would like to appear in the database answer field if the respondent (remote user) were to select this option. In this example the Option Button text says &#34;Yes I will be taking leave during this period&#34;, so an appropriate On Selection Database Field Value would be &#34;Y&#34; or &#34;YES&#34;. 
     In some cases, the on selection database field value may be chosen automatically. In particular, where the question is in the form of a option buttons grid, having a plurality of rows and columns, each row and column having a heading and specifying a plurality of points (cells) in the grid for selection by a respondent (remote user), a single column heading may be available in the database and the field value entered in response to answering of the question by a respondent (remote user) may be automatically selected from components of the row and/or column heading for the particular option selected. It will be appreciated that selected field values could be automatically selected for other types of question, as well as option buttons grid. 
     Never Seen Database Field Value--If the question has not been presented to the respondent (local user) due to the fact that their answers have taken them down another route the never seen database value will appear in the database answer field. 
     For Example: There may be a series of questions within the survey document that apply to one particular group and not another ie. Males--Females, Wage earner--Salary earner etc. 
     The database field value defaults to &#34;BY PASSED&#34; or &#34;NOT ACCESSED&#34;. This can be edited here on each question, or can be permanently changed for this and all future survey documents by using the TOOL/OPTIONS menu. In this example the author (local user) will not change the Never Seen Database Field value. Now the author (local user) presses Enter or clicks OK. 
     This has now completed the process of editing the variables for the first option of the first question. If the author (local user) presses Enter or clicks OK, he will now see the question option text appear in the question box. 
     To complete the range of options available to the respondents(remote users) the author (local user) must repeat the above mentioned process on the next two options. However, as this is an option button based question there will be only one database column and therefore there is no need for the author (local user) to nominate either the Database Column Heading or the Never Seen Database Field Value again. 
     Lets assume that your three options are as follows: 
     
         ______________________________________
               On Selection
               Database Field
Option Button Text
               Entry         Branching to
______________________________________
Yes I will be taking leave
               Y             {NEXT}
during this period.
No I will not be taking
               N             {FINISH}
leave during this period.
I am not sure at this
               M             {FINISH}
time.
______________________________________
 
    
     See FIG. 8 for a screen display of the question text and allowable answers. 
     The author (local user) then saves the work he has done so far by selecting the FILE/SAVE menu option. The survey document may be given a unique and descriptive name. Such as HOLIDAY.SVM. 
     The author (local user) can now go ahead and create the final question in the survey document. To start a new question the author (local user) must select the QUESTION/NEW QUESTION menu option. This will present the author (local user) with a new question box containing, as before, the &#34;NEXT&#34; and PREVIOUS buttons as well as the Question Text area. The author (local user) can now proceed as per the first question but using the new set of variables. 
     Lets assume that the final question is an option-type question and the parameters are as follows: 
     
         ______________________________________
Field                 Variable
______________________________________
Question Text         Where will you be
                      holidaying
Question Title        Destination
Database Column Heading
                      Destination
Never Seen Database Field Value
                      BY PASSED
Option One: Option Text
                      New South Wales
Option One: Branching To:
                      {FINISH}
Option One: On Selection
                      NSW
Database Field Value
Option Two: Option Text
                      Australia, but not
                      NSW
Option Two: Branching To:
                      {FINISH}
Option Two: On Selection
                      AUST
Database Field Value
Option Three: Option Text
                      Overseas
Option Three: Branching To:
                      {FINISH}
Option Three: On Selection
                      OS
Database Field Value
______________________________________
 
    
     Now that the second and final question of this brief survey document has been completed the author (local user) can take a look at the linking of options from question one (LEAVE) to question two (DESTINATION) or FINISH (end of survey document). 
     Earlier the Branched-To Question field was mentioned and the author (local user) used the {NEXT} and {FINISH} options because he could not nominate the &#34;Question Title&#34; of the next question at that point. Now that the next question has a title, &#34;Destination&#34;, the &#34;Branching To&#34; field in the previous question that contained the {NEXT} option will automatically change to read (DESTINATION). 
     So in summary, the author (local user) has asked a question relating to leave being taken and another relating to where the respondent (remote user) will be taking this leave. Now clearly if the respondent (remote user) has answered either option two or three (No and Not sure) to the first question (LEAVE) there is no need for them to answer the second question (DESTINATION) and therefore they should go straight on to (FINISH). Option one (Yes I will be taking leave during this period) of question one (LEAVE) should lead to question two (DESTINATION). As the second question is also the last the author (local user) may choose settings of {FINISH} as all options will need to lead to the end of the survey document. 
     Although in this example the author (local user) has chosen the {NEXT} option to automatically handle his linking it can be done manually using the following process. 
     The first thing to do is to get the first question (Leave) back on the screen. This is done by is selecting the QUESTION/GOTO QUESTION menu, and the choosing of &#34;LEAVE&#34; of the list (FIG. 9). 
     Question one (LEAVE) is now displayed on the screen. Double clicking on the first option (Yes I will . . . ) will display the option button properties dialogue box. From the list displayed in the Branched-To Question section select the second questions title &#34;DESTINATION&#34; and press Enter or click OK. 
     The final step before testing is to nominate which question is the first question to be presented to the respondent (remote user). This is done by selecting the QUESTION/SET FIRST QUESTION menu and nominating the Question Title of the appropriate question. 
     The first test that the author (local user) should perform is the SCAN TEST. This is accessed through the TOOLS/SCAN menu option (FIG. 15). 
     On selecting SCAN TEST the arrangement scans through the survey document and searches for any errors in the question structure. This is particularly important for complex survey documents which incorporate a number of branched-to questions. SCAN TEST generates a report of &#34;orphans&#34; and &#34;cul-de-sac&#34; ie., questions which no other questions lead to and questions which do not lead to anything. The arrangement is aware that there is a single question which will not have a preceding question (the question selected as the first question in the survey document) and a single question which will not have a succeeding question (the last question in the survey document). It may test all the other questions simply to determine for orphans or cul-de-sacs. Once any existing orphans or cul-de-sacs have been identified the author (local user) can access them to correct them. 
     In addition to orphans or cul-de-sacs SCAN TEST also identifies any Cross Linked Questions (A child question that branches to any preceding question) and Duplicate Database Field Names. It will also test for illegal names (e.g. over eight characters for DOS based database) and missing names. 
     In one embodiment, an entire list of the items appears on the authors (local users) screen. Clicking on one item immediately takes the author (local user) to that item. By &#34;item&#34; is meant any item which may be determined by the local user in preparing the Survey Document, e.g., Goto&#39;s, not accessed, branching-to questions, DatabaseFieldName, etc. The listing will not include information such as question text (although the Question title is listed) and the like which do not effect the mechanical structure of the Survey Document (e.g., the pathway through the Survey Document). It is a mandatory requirement, however, that the author enter Question Text. While this will not affect the mechanical operation of the document (the way it runs on the respondents processor), if no Question Text is provided, the respondent user will view a blank question (i.e., no question). A test for question text is therefore important and is included. There may be other mandatory items such as question labels. 
     The listing enables the author to briefly check that the document structure reads as desired. Any items identified by the scan test as being in error are preferably highlighted in the listing so that the user can click on them and take the appropriate action to correct the error. An embodiment is envisaged where all variables in the Survey Document which could be effected by the author or system configuration are listed. 
     Once the SCAN TEST has been completed without error the author (local user) can be confident that the mechanics of their survey document are in order. 
     The Respondent Test is accessed either via the TOOLS/TEST FROM TOP (FIG. 15) or by a simple click on a &#34;Test&#34; icon on the tool bar. 
     Activating Respondent Test will take the author (local user) through the survey document as if he where a respondent (remote user). 
     A further test is TOOLS/TEST FROM CURRENT (FIG. 16) this allows the local user the option of testing the Survey Document from any particular question he is currently displaying. 
     Prior to sending the survey document the author (local user) determines the electronic mail address the response documents are sent to FILE/SET REPLY ADDR (FIG. 15) and then nominates the return address. 
     Once the author (local user) is satisfied that the survey document works and that the response will be going to the correct mail address he may send it to his target audience. 
     To do this he selects the FILE/SEND SURVEY (FIG. 16) menu option (FIG. 10). 
     The Survey Author Module assumes that the author (local user) will be sending the survey document that is currently loaded. 
     It will present a dialogue box listing of all the respondents (remote users)and groups of respondents (remote users) that the author (local user) could mail to. The survey author may also mail to the respondents of previous surveys. A listing of the respondents of previous surveys is kept. The dialogue and box will also list all the previous surveys so that the author may click on a selected previous survey to send to remote users who filed responses for that survey. Methods may also be used to select sub groups within the targeted database. The author (local user) will make his selection and press Enter or click OK. Another dialogue box will appear enabling the author (local user) to attach a message to the survey document. For example the author (local user) could use this to introduce the survey document to the respondents (remote users) and explain the benefits to them or the organisation of responding to it quickly. Once the author (local user) is satisfied that everything is OK he can press Enter or click OK. The small survey document will then be on its way to its target audience. At the same time (in the preferred embodiment, just prior to transmission) the apparatus will automatically create the database in preparation for the responses. Also, at the point that the local user selects the FILE/SEND survey menu from the File menu they are offered a dialogue box requesting them to name the SVQ (survey document to be sent out) file that is about to be sent out. The default name is that of the SVM (the survey document master--see later). Once the local user has either selected a new name for the SVQ or accepted the default name the local user will be offered another dialogue box asking for them to select the database type that they would like to create for this survey to be collated into. At this point the local user will ask for either a database name and/or table name. The default will be the SVQ name. However, the local user can change it. 
     The database can be fully populated if the author is mailing the survey to a list of known users. However, there is the option for the database not to be populated if their survey is sent to a group, for example, or put on a bulletin board. In the present example, the database is fully populated. 
     See FIG. 14 for a diagrammatic representation of the database. The database is comprised of three columns and N+1 respondent (remote user) rows, where N is the number of respondents (remote users) (+1 is the row containing the column headings). The three columns include two columns for the two respective questions, and a column which contains respondent (remote user) ID. Note that a number of fields may be necessary for a users mail address. The columns and rows intersect in matrix form to provide database answer fields in the form of cells, for the entry of the appropriate field value as answer documents are processed. 
     Each remote processing apparatus may be configured with a &#34;Survey User Module&#34; or recipient module (response module) to enable preparation of an answer document in answer to the survey document. The Survey User Module will be installed either on the server that the respondent (remote user or recipient) is attached to in the network, or on the respondents (remote users) machine. 
     Alternatively, the recipient module may be transmitted with the survey document, so that a respondents users computer need not even be configured to be able to process the survey document. Instead, the recipient module transmitted with the survey document will configure the respondent users computer. 
     The respondent (remote user) will generally access the survey document through their normal electronic mail procedure. Where the respondent (remote user) is not connected to electronic mail, he may receive the survey document by another communications medium, eg. by normal mail, or by any other means. They will read the mail that has accompanied the survey document and then use their mouse to select and launch the survey document. On their screen will appear the question one (LEAVE) dialogue. They will use their mouse to select the option that applies to them. They will then click on next. Depending on their selection either the (FINISH) or the (DESTINATION) dialogue box will appear. Once they have answered all the questions the (FINISH) screen (FIG. 11) will appear thanking them for the involvement in the survey. Once they press Enter or click Finish all of their answers will be transmitted back to the Survey Collator Module automatically. 
     The local processing apparatus, in particular the Survey Collator Module is arranged to monitor incoming transmissions via electronic mail other means, even manual entry) to identify answer documents for the particular survey. The &#34;Survey Collator Module&#34; is applied to gather all the incoming responses and load them in the database. In the preferred embodiment, as described below with reference to FIG. 12, the Survey Collator Module has a number of functions, operation of which may be dictated by the collator (local user). 
     Note that the Survey Collator Module may be entered on a different processing apparatus to the processing apparatus which the author (local user) used to prepare the survey document. This arrangement will be particularly useful where the author (local user) makes heavy use of a particular computer and, although he may wish to prepare the survey document using that computer, he does not wish machine time to be taken up with collation of answer documents. He can therefore designate another machine to receive and collate the answer documents. 
     Survey Collator Module--As previously explained this module of the application gathers all the incoming responses and puts them in a database ready for analysis. When this module is first launched the collator (local user) must select the SURVEY/PROCESS menu. The collation process is automatic. An options menu is provided which enables the local user to select whether a particular survey should be &#34;activated&#34;, &#34;suspended&#34; or &#34;terminated&#34;. When a survey is &#34;activated&#34; the collator will automatically collate all response documents relating to that survey. When a survey is &#34;suspended&#34; (d1 in FIG. 12), the collator will receive and identify response documents relating to the survey but will not process them. It will merely store them. When a survey is &#34;terminated&#34; the collator will identify all response documents relating to that survey and delete them upon arrival. 
     The Survey/Process menu will now attempt to logon and start the collation process. On loading the collator module it will not start the collation process until the Survey/Process menu has been selected. The way that the collator gets to know about the surveys is when the first response document comes in. When this happens the collator puts its name up on the screen along with information relating to the last date and time it received an entry and the total number of entries it has received for that survey to date. The collator will continue to collate the &#34;activated&#34; survey entries until the local user &#34;suspends&#34; the process. The local user can also decide to &#34;terminate&#34; the survey, in which case all incoming responses will be deleted upon arrival (see later for description of &#34;activated, suspended, and terminated&#34;). All surveys will list on the screen regardless of which of the three states they are in. The local user could decide to delete a survey from the list. However, if an answer document comes in it will attempt to restart the collation process. 
     FIG. 12(a) illustrates the main Survey Collator Module screen of this embodiment. The Survey Collator Module can handle a plurality of different surveys, exemplified in FIG. 12(a) by &#34;survey 1&#34; and &#34;survey 2&#34; under &#34;survey name&#34;. 
     Once the collator (local user) has done this the Survey Collator Module will automatically start the electronic mail if it is not already running and then start to scan for incoming responses. 
     On the screen the collator (local user) will notice that the Survey Collator Module tells him how many responses it has received and what percentage that amount represents of the total the survey document was sent to (&#34;Total #&#34;, &#34;# Read&#34;, &#34;% Process&#34;). The &#34;total&#34; and &#34;percentage process&#34; will only appear when the survey has been sent to a known list of respondents and a pre-populated database option has been chosen. Where the database is unpopulated, obviously the collator will not know how many respondents will be required to fill the database. 
     If after a few days the collator (local user) notices that the responses have slowed down to a trickle he may like to send all those who have not yet responded a quick reminder. This can be done automatically by selecting the SURVEY/REMIND menu option (FIG. 12 (b)). Having done this the collator (local user) will be asked to type a brief reminder message. Once the collator (local user) presses Enter or Clicks OK the Survey Collator Module will interrogate the nominated survey database and send the mail to all the non-respondents. This should prompt a few more to respond to the survey. However, if in a few more days the collator (local user) still has not received all the responses he may select SURVEY/RE-SEND menu (FIG. 12 (c)). This works the same way as REMIND but along with a message from the collator (local user) it will retransmit the survey document. 
     Once the collator (local user) is happy with the number or percentage of the responses received he can de-activate the survey document by selecting the SURVEY/TERMINATE menu option (FIG. 12(d) and 12(e)). This means that Survey Collator Module will discard all responses for this survey from now on. The database will contain audience responses for each user. If the respondent (remote user) does not respond this may be indicated in an extra database column (the &#34;respond column&#34;). 
     There is also the option of gathering various information available automatically on the E-Mail system. For example, postcodes, telephone numbers, etc. Various database columns would be prepared to receive this automatically gathered information, which would not be part of the survey document received by the remote user. Further options include date/time stamping depending on the time the answer-document-was received and/or the ability to log whether this is a reply to an original survey or a reply to a reminder or a reply to a re-sent survey. Appropriate database columns would be required. 
     FIG. 12(g) illustrates &#34;Options&#34; available with the survey collator. 
     FIG. 13 shows a functional diagram of the survey system. The functional diagram shows in brief the steps discussed above of operation of the apparatus and method in accordance with the embodiment discussed above. At 100 the author creates a survey with a survey name 101 and mails it out to a remote user 105. Further, just prior to mailing of the survey, the database is created at 102, the questionnaire is prepared at 103, and the questionnaire is mailed to the Collator at 104. 
     At the remote user end of the system, at 106 the user reads and processes the survey and creates an answer document at 107 and sends 108 by mail back to the collator. 
     At the local user end, at 109 the collator reads the questionnaire and notes the existence of the survey in its register. Later at 110 the collator reads the answer document and updates the database at 111 with the answer. 
     In operation, when the survey document has been completed prior to transmission it is a master. The document sent out is a subset of the survey master, known as the SVQ. The SVQ is saved for subsequent re-transmission, e.g., if reminders are required. At the point that the local user selects the FILE/SEND survey MENU OPTION from the file menu they are offered a dialogue box requesting them to name the SVQ file that is about to be sent out. The default name is that of the SVM. Once the local user has either selected a new name for the SVQ or accepted the default name the local user will be offered another dialogue box asking for them select the database type that they would like to create for this survey to be collated into (see above). As discussed above, at this point the local user will be asked for either a database name and/or table name. The default will be whatever the SVQ was named, although the local user can change it. The safeguard here is that the local user will not be able to select an existing database name or table name within an existing database. 
     Note that the SVQ is also preferably saved in collator, as reminders will most probably be sent from them. 
     One advantageous feature of a preferred embodiment of the invention, as briefly discussed above relates to the naming of the database column headings when a question and allowable answer utilise a numeric field grid or check box grid. For example, referring to FIG. 6, which illustrates a check box grid, it will be appreciated that there are 16 possible answers (check box cells) to this question. If the remote user has more than one car, he may check more than one cell. Sixteen database columns are therefore required. Manually choosing a name for each of these database columns would be laborious. To overcome this problem, the apparatus and method of a preferred embodiment of the present invention automatically designate database column headings which are formed from components of the column and row grid headings. For example, the name for the database column heading corresponding to the top left hand corner check box cell may automatically be set at &#34;sedan 4&#34;. Similarly with the rest of the check box cells. This naming technique can also be applied for a numeric field grid. The column heading may be formed from combining the entire column and row headings of the grid, as above, by combining components of both of them, or by using the column or row heading only or a component thereof. 
     For option button grids, where only one option is allowed to be chosen, in a preferred embodiment of the invention, as discussed briefly above, it is only necessary for the database to contain one database column, no matter the number of possible answers. In this case, the database field value to be entered in the database column in dependence on the remote users answer is chosen from components of the column and row headings of the grid. With the option buttons grid therefore, the actual field value to be entered is named from the headings of the rows and columns of the grid box cell selected. As discussed previously, option button grids may include a series of sub-groups requiring the remote user to select a single option item in each of the sub-groups. In this case, as many columns in the database will be required as their are sub-groups. 
     An advantageous feature of a preferred embodiment of the invention allows the database to be fully loaded prior to the survey document being sent out, in order to test whether the apparatus can accommodate the fully loaded database. 
     In the embodiment described above, when the remote user receives the survey document (SVQ) and processes it on his apparatus to produce an answer document (SVR), the SVR is sent back and the original mail message and the SVQ are deleted or the remote user is told to delete, so that they cannot be used again by the remote user. A further option exists for the Survey Author (local user) however, to provide an instruction that tells the remote users not to delete the SVQ when the answer document is sent back. This enables a requirement for regular information (weekly, monthly, quarterly) to be met by the remote user by simply re-running the SVQ on a regular basis. If such an option is utilised, the databases prepared to include a &#34;time received&#34; database column to indicate a time at which the particular answer document is received from the particular user. 
     The following is a description of the structure of a software implementation of the preferred embodiment of the present invention, a working example of which has been explained above generally from the point of view of user operation of the embodiment. 
     Software code has not been listed. The following description of the software modules and the various &#34;features&#34; they are required to execute will be sufficient, together with the following descriptions of the various documents (survey master document, survey question document and survey response document), and the previous description of the functions of the system, to enable a person skilled in the art to construct software. 
     This description does not describe the specifics of the user interface, as, except where certain operational rules are enforced, the specifics are fundamentally irrelevant to the description of the current embodiment. The operational rules will be covered at the end of this description. 
     The computer language used within this description when detailing structures is generic, but a person skilled in the art will easily be able to convert these details to an appropriate computer language. 
     Overview 
     The preferred embodiment is composed of three separate but related software modules: 
     Survey Authoring Module--herein known as the Author (local user) 
     Survey Recipient Module--herein known as the Recipient (remote user) 
     Survey Collating Module--herein known as the Collator (local user) 
     In the current embodiment all three modules are designed as Microsoft Windows applications, having been written and complied in Microsoft Visual C++ using Microsoft&#39;s MFC Class Library. All three modules interface to Microsoft E-Mail through the MAPI interface. Both the Author and the Collator modules access databases through Microsoft ODBC interface, allowing the system to work with almost all available databases. 
     Standard programming techniques have been used as much as possible to allow portability to other systems that support MFC. 
     There are three areas where slightly non-standard techniques have been used: 
     1. The presentation of the dialogue boxes in the Respondent module (and equally their presentation in test mode within the Author module) utilises a Windows feature of being able to present a dialogue box from a template in memory instead of the usual method of presentation from a static resource. This allows dynamic control of the appearance and content of the dialogue boxes from information stored in the questionnaire (SVQ). 
     2. At the point when the survey questionnaire is to be mailed to the remote users the Respondent module (Response Exe) is pre-pended to the actual questionnaire document (SVQ), given the `file-name` of the survey master document (SVM) and the extension `Exe`. 
     It should be noted that the SVQ is a C++ `object`, and to achieve data persistence its MFC archiving methods are used both to write it at the Author, and to reload it at Respondent. 
     When the remote user runs the composite file, the Respondent module start-up-code offsets the file pointer in the MFC standard archive read method to point to the SVQ section of itself. It then loads the data to `re-instantiate` itself, processes the data through the normal SVQ methods and presents the questions to the user. The composite file transmitted to the Respondents operates as a true `object` with encapsulated SVQ data. 
     (Note that an `object`, as will be understood by a skilled person, is a collection of executable methods that are specific to the encapsulated data types and structure (an `instance` of which is held within the object), and (generally) those methods are the only way for external agents (people or processes) to operate on that data). 
     3. Following on from (2) above, the final size of the composite file is largely determined by the number of executable SVQ methods which are mailed with the SVQ data. To increase efficiency through the E-Mail system the size of the composite file should be as small as possible. By using conditional compiles on the SVQ object, a common minimal `set` is used by the Respondent module, while the full `set` is available to the Author module. 
     The common minimal set will be a matter of choice of the skilled person, who will be able to establish the minimal set of methods required to run the SVQ by the respondent module. 
     The Author Module 
     The main functions of the Author module are the design of the questionnaire, preparation of an appropriate database, and the transmission of the questionnaire to the remote users. 
     All Author functionality is derived from the Survey Master Document (SVM) methods. 
     Note: the SVM contains the Survey Questionnaire Document (SVQ) inside itself so that all SVQ methods are available to the Author. Further the SVQ contains an array of `Question-Box objects` inside itself so that all Question-Box methods are available to the Author. The data members for the SVM/SVQ/Question-Box `objects` and the functionality of the more relevant methods are detailed below. 
     The Menu structure, as will be realised from the preceding description, is based as closely as possible on Microsoft `Office` products to achieve the highest degree of user interface compatibility with Microsoft standards and therefore facilitating ease of use. 
     The user interface for the dialogue box editing used in the creation of the question boxes is preferably based on several Microsoft and Borland `dialogue editors`. Other techniques could be used. 
     One of the underpinning interface design criteria has been to shield the Author user from the need to have any knowledge about databases. 
     The Author module generates default database field names based on the Question names, e.g., user question name as the field name. Users can change the database field names if they wish but there is no need to do so. 
     The database field types required are, in this preferred embodiment, deliberately limited to Boolean (Logical), Text and Numeric. Except for `Numeric` fields, the other types are automatically deduced by the Author module, and the user is shielded from the need to set the database field types. For `Numeric` fields the database field types default to `Integer` but the user may change them to `Decimal` (assumed 2 places) if they wish. 
     The database field length is automatically deduced for Boolean and Numeric fields, and a default calculation is performed for the length of Text fields based on the length of the field on the users&#39;s screen (which may be set by the survey author, as discussed previously). 
     In the interests of making life easier for the user various `features` are designed into the system for the preferred embodiment. 
     For the Quenstion&#39;s goto directives the Author defaults to a system specific value of `{Next}`. When a new Question is added, the Author module automatically retrofits the new Question&#39;s name into the previous Question&#39;s goto directives if they were set to `{Next}`. 
     Equally if the user changes the names of a Question all other questions are scanned to see if any of the other Quenstion&#39;s goto directives point to the current Question, and if so, their goto directives are changed to reflect the new names. 
     The scan test (part of the author module) tests for as wide a range of errors possible: 
     1. `Orphan` or `Cul-de-sac` questions. 
     2. Question Box text which has not been changed from the system default `Question Text for Question No. 001`. 
     3. Item (Option Buttons, Check Boxes, and Labels) text which has not changed from the system defaults (`Option Button Text 01`, `Check Box Text 01`, and `Label 01` respectively). 
     4. Duplicate database field names. 
     5. Any missing fields. 
     The author module automatically checks for missing, or duplicate or illegal database table names at the point of creation of the survey database. 
     A wide range of system defaults exist for the user to set the default size and position of the Question Box, default values for all the items, default values for the `Never Seen Value` and the default goto directive. 
     The author automatically generates the last Question (`{FINISH}`) when a new survey document is created. 
     When the user decides to mail out the survey to the remote users the following sequence occurs: 
     1. The user is presented with a list of E-Mail users (via the MAPI mail interface) for the remote users (or groups of remote users) to be selected. 
     2. The user is presented with a suitable `Subject and Note` dialogue box to advise the remote users about the survey. 
     3. The user is presented with a list of E-Mail users (via the MAPI mail interface) for the Collator E-Mail address to be selected. 
     4. The user is presented with standard ODBC dialogues for the selection (or creation) of the Data Set Name (DSN) for the required database. 
     5. This is followed by a dialogue box where the user is asked to enter the `table name` for the survey (defaults to the name of the survey). 
     6. The table is created in the ODBC database. 
     7. The SVQ section of the SVM is written to disk. 
     8. Respondent module (Response Exe) is pre-pended to the SVQ, given the `file-name` of the Survey Master Document (SVM) and the extension `Exe`. 
     9. The `composite object` of Response Exe and the SVQ is mailed to the selected respondents (and to the Collator E-Mail address) via the E-Mail system. 
     The Respondent Module 
     The composite file, containing both the Response Exe (the executable methods for the SVQ) and the SVQ `persistent data`, appear as an executable file attached to the E-Mail message containing the `Subject and Note` texts (mentioned in the Author module above). When the is user launches the attached executable its start-up-code offsets the file pointer in the MFC standard archive read method to point to the SVQ data section of itself. It then loads the data to `re-instantiate` itself, processes the data through the `common minimal set` of SVQ methods and presents the questions to the user. The answers are stored in the SVQ as the user works through the questionnaire. When the user finally exits the `{Finish}` terminating question, the answers are copied to the Survey Response Document (SVR). 
     As there may be hundreds (or thousands) of SVR documents arriving at the Collator&#39;s E-Mail address, the size of the SVR is extremely important. For this reason the SVR has been created separately from the SVQ. While the SVR&#39;s data members are exact copies of the associated data members in the SVQ the number of members is reduced to the bare essentials--see below for a description of the SVR structure. 
     Collator 
     The Collator works with 3 document types: 
     1. Its own `survey register` document, which is a list of current surveys including relevant associated information--see below. 
     2. The Survey Questionnaire document (SVQ). 
     3. The Survey Response Document (SVR). 
     The Collator&#39;s main function is to read incoming survey response documents (SVR) and update (or add) the respondents answer information to the appropriate ODBC database. 
     The Collators other functions are: 
     1. To read incoming survey questionnaire documents (SVQ) and register the new survey in the Collator&#39;s `register`. 
     2. To send reminders to entries in a pre-populated database that have not yet responded (i.e., the Mail Received Date field is still set to the default). 
     3. To re-send the Survey Questionnaire Document (SVQ) to E-Mail users that request a resend, or to entries in a pre-populated database that have not yet responded (i.e., the Mail Received Date field is still set to default). 
     Outside of the methods available to Collator through the document `objects` that it is `aware` of, the Collator is a straight forward and simple program. 
     Upon starting the Collator reads the E-Mail message queue to ascertain if there are any relevant messages of it. 
     If there are no relevant messages it goes to `sleep` for a period of time controlled through its user definable options (see FIG. 12). 
     If there are messages to process then it sits in a loop reading and processing messages up to a number specified again in its user definable options (see FIG. 12), or until there are no more messages to process, where upon it will put itself to `sleep` again. 
     If it has been `asleep`, it will re-enter the loop as if it had just started. 
     When it processes an SVR (assuming the associated survey has been registered) it will update the appropriate database and delete the E-Mail message containing the processed SVR. 
     When it processes an SVQ it will register the new survey in its `register` and copy the SVQ to a user definable directory for safe keeping. The surveys are registered with a default status of `Active` but the user may choose to set that initial status to `Suspended` to have manual control over when surveys are processed. 
     Collator E-Mail Messages 
     The Collator monitors the E-Mail in-tray. It searches for 2 types of E-Mail messages. 
     1. The copy of the Survey Questionnaire Document (SVQ) sent by the Authoring module at questionnaire transmission time, and 
     2. The Survey Response Documents (SVR) returned by the respondents (remote users). 
     Both these messages are coded with a signature so that they can be picked out from the normal E-Mail that may arrive. The signature indicates what types of message they are, but not which particular survey or database they belong to. Collator has to open the messages and read them to ascertain that specific information. 
     Collator Survey Status 
     Collator maintains a `register` where all the current and recent surveys that it is `aware` of are listed. Each survey has an associated status as discussed previously: 
     1. Active--the survey is being processed normally. The responses are being read, the database is being updated or added to and the read messages are being deleted once they have been successfully processed. 
     2. Suspended--the survey responses are ignored. Collator reads the message, ascertains that the survey is in a suspended state and advances to read the next E-Mail message. This state is set to temporarily isolate the database from the incoming E-Mail. This is useful for accessing the database before the survey is terminated, for staged analysis or repair. A suspended survey can either be re-activated or terminated. A survey may optionally be set to suspended the instant that it is registered. 
     3. Terminated--the survey is concluded. Any E-Mail associated with this particular survey will be read to ascertain its identity and then deleted without any processing. 
     Collator Survey Registration 
     Collator registration occurs as a result of receiving either the SVQ or an SVR E-Mail message for a survey that has not yet been `registered`. The survey is immediately stored in Collator&#39;s internal register, and the status is either set to `Active` or `Suspended` depending on the user options that have been set. A user may choose to set the `Suspended-on-registration` option if the user wishes to set the survey `cut-off` values before any of the responses are processed. 
     The associated database and the number of responses received is also stored in the register on a survey by survey basis. 
     If the default status for a newly registered survey is `Active` but a problem occurs when the associated database is being accessed, the survey will be automatically placed in a suspended state with a message indicating that an error occurred linking to the database when the survey was being registered. The E-Mail message will remain in the in-tray in this case until it is able to be processed correctly, or unless its status is changed to `Terminated`. 
     A survey entry in the Collator&#39;s register can be deleted if it is old and has been previously terminated. If an old response arrives after an entry has been deleted the Collator acts as if it is a new survey and will attempt to re-register the survey and to link to the database and process the response, unless the default registration option is to set a suspended state. 
     Collator Survey `Cut-Off` Levels 
     If the survey is using a pre-populated database then the exact number of responses is known and a `cut-off` level can be set in terms of either a `percentage complete` or a specific number of responses. If the survey is not using a pre-populated database then the `cut-off` level can only be set as a specified number of responses. 
     Once the `cut-off` level is reached the survey status is immediately set to `suspended`. The `cut-off` level can be left empty and the Collator will continue to process until the survey is manually `suspended` or terminated. 
     Collator Database Creation 
     An additional feature of the Collator and the format of the Survey Response Document (SVR) is that the database can be re-created from the information in the SVR. If the original database was pre-populated the fully populated database cannot be re-created, but the correct database structure can be reproduced and Collator, being aware of the `re-creation`, can change the database `updates` to `additions`. 
     This has two main advantages: 
     If for any reason the original database has been corrupted, destroyed or lost, and a sufficient number of responses has not yet been processed, the Collator can re-create the database, and the Author does not have to burden the remote users to re-respond to a previous survey. 
     If the survey instigator is in a location physically removed from the original database, but wishes to run Collator and process the responses, a new database can be created. 
     Collator Options 
     The Collator can be set to process continually or to sleep for a range of minutes and then awaken to process a specified number of responses only. 
     The Collator `resister` document structure 
     
         ______________________________________
WORD     wNumOFSurveys  Number of Surveys
______________________________________
WORD     wSleepMinutes  num of minutes to sleep
WORD     wMaximumGrab   max num SVRS to process
WORD     wDBNumOfRetries
                        max ODBC retries
WORD     wDBRetryWait   100th secs between retries
STRING   strSVQPathName SVQ directory name
BOOLEAN  bSortByName    sort by name or date
BOOLEAN  bAscending     sort ascending or descending
BOOLEAN  bHideTerminated
                        hide terminated from display
BOOLEAN  bSuspendOnRegister
                        suspend on registration
DATETIME LastScan       timestamp of last scan
ARRAY    SurveyRegister array of Survey info
The Survey Register Structure
WORD     wSurveyStatus  Status of the survey
WORD     wtotalResponses
                        total SVRs received
WORD     wProcessedResponses
                        number SVRs processed
WORD     wDeletedResponses
                        number SVRs deleted
WORD     wTotalRows     pre-populated total
WORD     wCutOffCount   holds cut off level
BOOLEAN  bRecreatedDatabase
                        indicates DB recreation
BOOLEAN  bPrePopulated  indicates pre-populated DB
BOOLEAN  bRetainAfterReply
                        indicates SVQ is kept
DATETIME tmRegistered   timestamp when registered
DATETIME tmCurrentStatus
                        timestamp of current status
DATETIME tmLastRead     timestamp of last SVR read
DATETIME tmRemind       timestamp of last Reminder
DATETIME tmResend       timestamp of last Resend
STRING   strSVQFileName name of SVQ file
STRING   strSurveyName  full SVM pathfilename
STRING   strTableName   Name of the Table
STRING   strDataSetName Data Set Name (DSN)
STRING   strDataSetConnection
                        Full DSN Connect string
ARRAY    DataSetDataTypeArray
                        Available Data Types Array
______________________________________
 
    
     The above-described modules access 3 document file formats collectively known as the Survey Documents: 
     1. the Survey Master Document (SVM), 
     2. the Survey Questionnaire Document (SVQ), and 
     3. the Survey Response Document (SVR). 
     The design of these Survey Documents underpins the Preferred embodiment. Whilst the preferred embodiment is implemented for MS Windows the design of the Survey Documents could easily be transferred to any computer system. The Survey Master Document (SVM) contains the Survey Questionnaire Document (SVQ), and also contains additional survey `author` information not required in the questionnaire (SVQ) section. The Survey Response Document (SVR), contains the answers and sufficient information to link to the database and sufficient information to re-create the database in the case of a catastrophic error. The Survey Master Document (SVM) 
     The SVM is composed of four main sections: 
     1. The Survey Questionnaire Document (SVQ); 
     2. Subject and Note Texts; 
     3. Array of Recipients; and 
     4. Document defaults and options. 
     1) Survey Questionnaire Document (SVQ) 
     The following lists the document variables in order. 
     
         ______________________________________
String   strSurveyMasterPathName
                         PathName of this survey -
                         long name for document
BOOLEAN  bFlagPrePopulate
                         Pre-populate Database
BOOLEAN  bFlagRetainAfterReply
                         Retain SVQ after Reply
BOOLEAN  bFlagFollowup   Indicates secondary Survey
String   FirstQuestionName
                         The first one to start with
String   SelectedQuestionName
                         Currently selected Question
                         Name
String   NextQuestionName
                         Next Question Name to be
                         selected
WORD     NumofQuestions  Number of Questions in the
                         survey
Strut    ReplyToInfo     The Collator&#39;s mail address
String   strTableName    Name of the Table
String   strDataSetName  Data Set Name (DSN)
String   strDataSetConnection
                         Full DSN Connection string
Array    DataSetDataTypeArray
                         Array of Data Types
                         available
Array    QuestionsArray  Each element is a
                         &#34;QuestionBox`
______________________________________
 
    
     The following is a description of the document variables. 
     The strSurveyMasterPathName is the full pathname of the survey master document itself. 
     The bFlagPrePopulate indicates that a pre-populated database is being used. The default value of this flag is False. If True this flag has several implications; 
     1. the Survey Authoring Module will create and pre-populate the database with the E-Mail name and address, default mail received date and each question&#39;s `bypass` values; 
     2. the Respondent Module will set the Survey Response Document (SVR) to `update` and not `insert` records to the database; 
     3. the Collating Module responds to received SVR with this flag set to true by displaying percentage received figures as well as numbers of responses received. Also the Collating module allows the use of `reminds` and re-sends&#39; if this flag is set to true; and 
     4. all three modules are aware that if this flag is set then the index on the database is unique only on the name and address, and does not include the mail received date. Equally, if this flag is false it indicates to all three modules that the database is indexed on name, address and mail date received, so as to allow multiple responses from each respondent. 
     The bFlagRetainAfterReply indicates to the Respondent Module that it should indicate to the remote user to keep the current Survey Questionnaire Document (SVQ) rather than delete it on completion. The default state of this flag is false. 
     The bFlagFollowUp indicates to the all modules that some of the mail addresses being used are from previous surveys and may no longer be valid on completion. The default state of this flag is false. 
     The FirstQuestionName stores the name of the question to be first selected from the QuestionsArray. 
     The SelectedQuestionName is simply a current storage place for the name of the current Question. 
     The NextQuestionName is loaded by the control logic with the name of the next Question to select. 
     The NumOfQuestions is simply a storage area to record the number of Questions in the survey. 
     The ReplyToInfo structure contains the E-Mail name and address to reply to the Collator via the E-Mail system. The structure contains: 
     
         ______________________________________
String             MailName
String             MailAddress
LONG               MailEntryIDSize
Array              MailEntryIDData
______________________________________
 
    
     The fields are specific to MS Mail, but can be extended for any electronic mail or electronic bulletin board systems. The purpose of these fields is to store the Collator&#39;s mail address in the message that is sent to the Respondents. Note the Collator&#39;s mail address may not be the same as the Author&#39;s mail address (see previous description). The Author selects the Collator&#39;s mail address just prior to the Survey Document being sent to the Respondents. 
     The strTableName contains the name of the table to use within the specified database. 
     The strDataSetName contains the DSN that specifies on the local user&#39;s computer which database to use. The DatabaseSystem is specific to MS ODBC, but can be extended for any database system. 
     The strDataSetConnection contains the full ODBC connection string that is the complete identification string required to access the ODBC database. 
     This facility is useful where the local user may require periodic update of the same survey, eg. political poling. Out of date information would be overwritten by the new information coming in from the remote users, and the database &#34;date received&#34; field would indicate the latest date which an answer has been received from the remote. 
     2. Subject and Note Texts 
     
         ______________________________________
String     MailSubjectText
                         E-Mail Subject Text
String     MailNoteText  E-Mail Note Text
______________________________________
 
    
     The MailToSelection stores the operator&#39;s selection of who the mail recipients are. 
     The MailsubjectText is a simple one line description of the mail being sent to the Recipient. 
     The MailNoteText is used for a description of the survey, read by the Recipient before they begin the survey. 
     3) Array of Recipients 
     The recipients data is exactly the same as reply to info accept that it is an array of them. 
     
         ______________________________________
Array   RecipientsArray   Each element is a
                          &#34;RecipientDate`
______________________________________
 
    
     Again the actual `RecipientDate` structure implemented in the current embodiment is specific to MS mail, but can be extended for any electronic mail system. 
     Note this is not a fully expanded list--just simply what the operator chose. It may be any combination of individuals or E-Mail groups, or the E-Mail names and addresses of Respondents from previous surveys. 
     4. Document defaults and options 
     
         ______________________________________
WORD            wQuestionBoxLeftMargin
WORD            wQuestionBoxTopMargin
WORD            wQuestionBoxWidth
WORD            wQuestionBoxHeight
WORD            wQuestionTextWidth
WORD            wQuestionTextHeight
WORD            wQuestionTextLeftMargin
______________________________________
 
    
     The DataSetDataTypeArray is a list of the data types available for the chosen database. This information is used in the creation of the database. 
     The QuestionsArray is an Array of Question Box structures which contain all necessary information to present a question to the remote user. The `QuestionBox` structure is explained after the description of the Survey Document&#39;s main sections (see `The Question Box Structure` below). 
     Note: the Question Box array is accessed by use of the desired Question Box&#39;s `RefName`; equally when a Question Box is placed in the array the `RefName` is extracted from the Question Box structure and used as the index associated with the array. 
     Note that the bFlagPrePopulate flag is set to false where, for example, the Author is sending a survey to an electronic bulletin system. 
     As has previously been mentioned, application of the invention to a &#34;bulletin system&#34; would involve posting a Survey Questionnaire Document (SVQ) on a &#34;bulletin board&#34; for selection and answer by any user having access to the bulletin board. That is, the users would not be preselected for the Survey Document to be sent to. In such a case, the database size would depend upon the number of answers received to the Survey Document. 
     As discussed above bFlagRetainAfterReply flag when false indicates to the Recipient that it should erase the copy of the composite file when the Recipient has successfully sent back an answer (SVR). However if this flag is false then the SVQ may be preserved and used again. The bFlagRetainAfterReply flag when true also tells the Author and the Collator that each recipient may send more than one answer (SVR), and therefore an extra `DateReceived` field is generated in the database. This extra field is used to make the answer rows in the database unique for indexing purposes, and also to track the arrival of each of the multiple answers. 
     
         ______________________________________
WORD            wQuestionTextTopMargin
WORD            wControlsLeftMargin
WORD            wItemsLeftMargin
WORD            wCentreQuestionText
String          strNeverSeenValue
String          strNeverSeenSelection
String          strOptionChosenValue
String          strOptionChosenSelection
string          strCheckBoxTrueValue
string          strCheckBoxTrueSelection
String          strCheckBoxFalseValue
String          strCheckBoxFalseSelection
String          strNumericFieldType
String          StrNumericTypeSelection
String          strGotoDlgName
String          strGotoDlgSelection
______________________________________
 
    
     These fields are used as a place to store Author defaults for the creation of each of the Question Boxes by the Author. They are a convenience for the operator of the system, but not relevant to this description. 
     The Question Box Structure Overview 
     From the Recipient&#39;s perspective a Question Box is simply a standard graphical user interface `dialogue box` with: 
     1. The question text in an area at the top of the Question Box; 
     2. some user controls; either option buttons, check boxes, numeric data entry fields, or text data entry fields; and 
     3. two push buttons at the bottom of the Question Box, marked `Previous` and `Next`. 
     The Question Box structure must contain and/or achieve the following: 
     1. Sufficient information to display the Question Box via the graphical user interface; 
     2. define the Question Box&#39;s database field&#39;s name, type and size in the Author or Collator created database; 
     3. store the Recipient&#39;s answers in all the Question Box&#39;s database fields; 
     4. store the `Never-Seen` values as the Recipient&#39;s answers in all the Question Box&#39;s database fields if the particular question is never asked due to Question Box `branching`; 
     5. store the `Branch Control Language` script for this particular question if required (see later); and 
     6. define the name of the next Question Box to `goto` depending on the user&#39;s current or previous answers. 
     To achieve this there is a three tiered structure: 
     1. The Question Box or header containing several `GroupData` structures; 
     2. the `GroupData` structures which in turn contains several `ControlData` structures; and 
     3. the `ControlData` structure. 
     These three structures are detailed after the next section. 
     Constants/definitions used by all three structures 
     Each control is assigned a `TYPE` indicator. This is used to ensure consistency between the control and its Group. The controls are grouped by `TYPE`. 
     
         ______________________________________
define   CTL-TYPE-NULL       0×00000000L
define   CTL-TYPE-QUESTIONTEXT
                             0×10000000L
define   CTL-TYPE-NEXTPREVBUTTONS
                             0×20000000L
define   CTL-TYPE-OPTIONBUTTONS
                             0×00000001L
define   CTL-TYPE-CHECKBOX   0×00000002L
define   CTL-TYPE-NUMERIC    0×00000004L
define   CTL-TYPE-TEXT       0×00000008L
These defines indicate the `TYPE` of each Group.
define   GRP-TYPE-NULL       0×00000000L
define   GRP-TYPE-QUESTIONTEXT
                             0×10000000L
define   GRP-TYPE-NEXTPREVBUTTONS
                             0×20000000L
define   GRP-TYPE-OPTIONSBUTTONS
                             0×00000001L
define   GRP-TYPE-CHECKBOX   0×00000002L
define   GRP-TYPE-NUMERIC    0×00000004L
define   GRP-TYPE-TEXT       0×00000008L
define   GRP-TYPE-GRID       0×00000100L
______________________________________
 
    
     The Question Box needs to indicate what `TYPEs` of group/controls it contains. Note; 
     1. The first 4 are simple types. 
     2. The `GRID` is used in conjunction with the first 4 TYPEs to indicate which TYPE of `grid` it is. 
     
         ______________________________________
define   DLG-TYPE-NULL      0×00000000L
define   DLG-TYPE-BASE      0×30000000L
only PUSHBUTTONS &amp; STATICTEXT
define   DLG-TYPE-FINISH    0×30000000L
only PUSHBUTTONS &amp; STATICTEXT
define   DLG-TYPE-OPTIONBUTTONS
                            0×00000001L
define   DLG-TYPE-CHECKBOX  0×00000002L
define   DLG-TYPE-NUMERIC   0×00000004L
define   DLG-TYPE-TEXT      0×00000008L
define   DLG-TYPE-GRID      0×00000100L
______________________________________
 
    
     Following defines are for masking out the 3 sets of TYPEs: 
     
         ______________________________________
define   STANDARD-TYPES-MASK
                          0×F0000000L
Standard (StaticText &amp; PushButtons)
define   ACTIVE-TYPES-MASK
                          0×000000FFL
Active (Option, Check, Numeric, Text)
define   COMPLEX-TYPES-MASK
                          0×0000FF00L
______________________________________
 
    
     Complex (Grid and Combo indicators) 
     The ControlData Structure 
     The ControlData structure is mainly concerned with displaying the controls within the Question Box&#39;s dialogue; therefore they are based on MS Windows ControlData structure. However it is the additional fields that are important, as each graphical user interface will store its control&#39;s data slightly differently. 
     Also please note the standard MS Windows IDOK define is allocated to the `Next` button, and the IDCANCEL to the `Previous` button. This is pure convenience--any define will do. 
     Attributes as per MS Windows structure 
     
         ______________________________________
WORD      wX             X pos in dlg units
WORD      wY             Y pos in dlg units
WORD      wWidth         Width in dlg units
WORD      wHeight        Height in dlg units
WORD      wControlID     ID for messages from the
                         control
DWORD     lControlStyle  Window Style -
                         Option/Check, Default,
                         Group etc
BYTE      bClassID       Class ID - Button, Edit,
                         Static, etc
String    ControlText    Control Text
BYTE      bBytesToNextControl
                         Always null
______________________________________
 
    
     Attributes additional to MS Windows structure 
     
         ______________________________________
DWORD     lControlType  Type of Control (Option
                        Button, Check Box, etc)
String    FieldValueSelected
                        Value of database-field if
                        this Control is selected
String    ItemLabel     Name used to reference the
                        control through the BCL
String    GotoQuestionName
                        See explanation below
______________________________________
 
    
     The 1ControlType is used to cross check the control within the parent group structure. 
     The FieldValueSelected holds the value to place in the database field should Control be selected by the Recipient&#39;s operator. Note this is only applicable to Option Buttons and Check Boxes, as Numeric Field and Text Field entries are not predetermined. The database field itself is in the parent group structure. 
     The ItemLabel field is used to name the control (`item` in the Author operators menu) so that it can be referenced by the `Branching Control Language` (BCL--see later). The ItemLabel must be uniquely named within the Question Box but does not have to be unique across the whole Survey Document. The Author module will produce default labels based on the item type (Option Button, Check Box, Numeric Field, etc) and its sequence number within the Question Box. 
     The `GotoQuestionName` field is known by four different names when referred to from outside the ControlData structure. These are: 
     
         ______________________________________
1. GotoQuestionName
                 if the Control TYPE for
                 this is a CTL-TYPE-
                 OPTIONBUTTON, then this
                 field contains the GOTO
                 QuestionName, which will
                 placed in the `Next`
                 buttons `NextQuestionName`
                 should the Recipient&#39;s
                 operator select this
                 control. The value
                 (RefName) of the
                 GotoQuestionName is chosen
                 by the Author at design
                 time.
2. NextQuestionName
                 if the Control ID for this
                 is `NEXT` ie ControlID -
                 IDOK, then this field
                 contains the GOTO Next
                 QuestionName - chosen by
                 the Author at design time
                 or by the Recipient at
                 runtime (if Option Buttons
                 questions).
3. PrevQuestionName
                 if the Control ID for this
                 is `PREV` ie ControlID =
                 IDCANCEL, then this field
                 contains the previous
                 QuestionName that the
                 Recipient just came from
                 (at runtime).
4. FieldValueUnChecked
                 if the Control TYPE for
                 this is a CTL-TYPE-
                 CHECKBOX, then the GOTO
                 Name is Not Used | However
                 an extra `UN-CHECKED` field
                 value is required for a
                 CheckBox - so this field is
                 used to save space.
______________________________________
 
    
     The GroupData Structure 
     The GroupData structure is independent from the requirements of displaying a dialogue box through the graphical user interface. The GroupData structure contains all the information about a database field, and contains an array of the ControlData structures that are associated with that database field (which contain or will contain the Recipient&#39;s answer). 
     Each group contains ONE database-field, so: 
     1. There may be MANY Option buttons in a group. 
     2. There may only be ONE Check box in a group. 
     3. There may only be ONE Numeric Data Field in a group. 
     4. There may only be ONE Text Data Field in a group. 
     Attributes 
     
         ______________________________________
DWORD        lGrpType
Specifies Group Type - Option, Check, Numeric, Text
CString DataBaseFieldName
DataBase Field Name for this group of control(s)
WORD         wDataBaseFieldType
DataBase Field Type
WORD         wDataBaseFieldLength
DataBase Field Length
String       NeverSeenFieldValue
Value for database field if never displayed to Recipient
String       ResultantFieldValue
Final Value for database field when selections made
WORD         wSelectedControlID
ID of the Control the Recipient selected
BYTE         bNumOfControls
Number of controls in the Group
Array        ControlDataArray
Each element is a `ControlData`
______________________________________
 
    
     The lGrpType specifies the Group Type (Option Button, Check Box, Numeric Field, etc.) and is used as a cross check against the Group&#39;s ControlData elements. 
     The DataBaseFieldName, wDataBaseFieldType, wDataBaseFieldLength are used in the creation of the database by the Author. Also these fields are used by the Collator when loading the Recipient&#39;s answers into the database. The DataBaseFieldName must be uniquely named across the whole Survey Document. 
     The NeverSeenFieldValue holds an Author designated value to be placed in the database field if the Question Box was never displayed to Recipient. When the Recipient first opens the Survey Document then the ResultantFieldValue (see next) is pre-loaded with the NeverSeenFieldValue. Equally the ResultantFieldValue are loaded with the NeverSeenFieldValue if the Recipient&#39;s operator presses the `Previous` button thereby nullifying a selection. 
     The ResultantFieldValue holds the Recipient&#39;s answer to the question or the NeverSeenFieldValue field if the Question Box was never displayed to Recipient. 
     The wSelectedControlID holds the binary ID of the Control that the Recipient&#39;s operator selected. This is preserved in the answer document for debugging purposes, and allows the Recipient&#39;s selections to be replayed from the first Question Box. 
     The bNumOfControls tells the code accessing the Group structure the number of ControlData elements stored in the ControlDataArray (see next). 
     The ControlDataArray stores the `ControlData` elements. Note that the mechanisms that store and retrieve ControlData elements from/to the ControlDataArray does a cross check of the Control&#39;s Type and the Group&#39;s Type. 
     The OuestionBox Structure 
     The QuestionBox structure is based on MS Windows DialogHeader structure. However it is the additional fields that are important, as each graphical user interface will store its dialogue&#39;s data slightly differently. 
     Attributes as per MS Windows structure 
     
         ______________________________________
DWORD     lQuestionStyle
                        Specifies the Dialogue&#39;s-
                        Window Style
BYTE      bNumOfControls
                        Number of controls in the
                        dlg box
WORD      wX            X pos in dlg units
WORD      wY            Y pos in dlg units
WORD      wWidth        Width in dlg units
WORD      wHeight       Height in dlg units
String    MenuName      Menu Name - usually nul
String    ClassName     Class Name - usually nul
String    Caption       Title. / Caption on the dlg
                        window
WORD      wPointSize    Pointsize of loaded font
String    FontName      Name of loaded font
______________________________________
 
    
     Attributes additional to MS Windows structure 
     
         ______________________________________
DWORD     lQuestionType  Question Box Type
String    RefName        Question Box
                         reference name
String    PrevRefName    Records where
                         Recipient came from
String    NextRefName    Records where
                         Recipient went to
String    GotoScript     Optional `BCL`
                         Script to be
                         activated by `Next`
                         button.
WORD      wQuestionNumber
                         Records the Question
                         creation sequence
WORD      wNumOfGroups   Number of Groups in
                         the Question box
Array     GroupArray     Each element is a
                         `GroupData`
______________________________________
 
    
     The lQuestionType is used by this embodiment to restrict the Group `TYPEs` per Question Box--i.e., only one group of Option buttons, or several Check box groups, but not a mixture of both. The `lGrpType` sets the `TYPE` of the Group and does not check for compatibility with its parent question box `TYPE`--this restriction is controlled through the Question Box only--allowing for extensions to multiple group `TYPEs` if required for other embodiments. 
     The RefName is used when accessing the desired Question Box within the Question Box array, equally when a Question Box is placed in the array the `RefName` is extracted from the Question Box structure and used as the index associated with the array. 
     The PrevRefName is used to store which `previous` Question Box&#39;s RefName the Recipient came from, so that if the Recipient&#39;s operator presses the `Previous` button then the Recipient can return to the previous Question Box. 
     The NextRefName is used to store which `next` Question Box&#39;s RefName the Recipient went to. This is preserved in the answer document for debugging purposes, and allows the Recipient&#39;s selections to be replayed from the first Question Box. 
     The GotoScript contains an optional `BCL` (see below) program script to be activated by the `Next` button. The `Next` button can either: 
     Be loaded with the RefName of the next Question Box to branch to. 
     Cause (in the case of option buttons) the RefName of the next Question Box to be loaded from the selected Option Button&#39;s ControlData structure. 
     Cause, if the GotoScript is not null, the GotoScript to read and run to compute the RefName of the next Question Box. 
     Note, that the GotoScript if present will override any other goto logic that may have been implemented by the Author. 
     The wQuestionNumber records the sequence in which the Question Boxes were created, and is used to construct an initial computer generated RefName and Caption for each Question Box. 
     The wNumOfGroups stores the number of Groups in the Question Box&#39;s GroupArray. 
     The GroupArray contains `GroupData` elements. Note that a variety of mechanisms exist for the storing and retrieving of GroupData elements in the GroupArray, including access with consideration of desired `TYPE`, etc. 
     The Survey Response Document (SVR) 
     The SRV is fundamentally a stripped down SVQ. It will be appreciated that having answered the questions we no longer need the question or answer texts. We simply need to store the answer values (bypassed or answered), the database field names, the database field types and the database field lengths. The strSurveyMasterPathName field of the SVQ is retained as it contains sufficient information to identify the survey for the Collator&#39;s needs. Equally the strTableName, strDataSetName, strDataSetConnection, and DataSetDataTypeArray fields from the SVQ contain sufficient information to reconnect to or recreate the ODSC database created by the Authoring module. 
     The Survey Documents various stages 
     This description refers to FIG. 13. 
     At 103 when the Author operator chooses `Send` the Author does the following steps: 
     1. The operator is asked to select an E-Mail address for the Collator, which is stored in the ReplyToInfo section of the Survey Questionnaire Document (SVQ) stored within the Survey Master Document (SVM). 
     2. The operator is presented with an E-Mail address selection dialogue. The operator selects various individuals and E-Mail groups. These selections are placed in the MailToSelection section of the Survey Master Document (SVM). As discussed previously, E-Mail addresses of respondents to previous surveys may also be selected. 
     3. The operator is also presented with a Mail Subject Text and Mail Note Text dialogue. These fields are placed in the Subject and Note Texts section of the Survey Master Document (SVM). 
     4. The MailToSelection is decoded by the Author into individual E-Mail addresses and stored in the Array of Recipients section of the Survey Document. 
     5. The database is then usually created, its reconnection information stored in the strTableName, strDataSetName, strDataSetConnection, and DataSetDataTypeArray section of the Survey Questionnaire Document (SVQ), and a row for each of the Recipients (assuming bFlagPrePopulate is true) is preloaded with additional fields such as the Recipient&#39;s E-Mail name and MailID, and other fields as may be set by the Options section of the program. 
     6. If there is no room for the full database then the operation can be aborted without having sent the survey. 
     7. At this point the Author saves the Survey Document with its master extension .SVM. 
     At 100 the Survey Questionnaire Document (SVQ) section of the Survey Master Document (SVM) is extracted and written to disk, where it is combined with its associated `methods` (Response Exe) to form a composite object (both data and executable code). The Mail Recipients and the Subject and Note texts are copied to the mail system for the SVQ to be sent to the respondents. At this point the SVQ is also mailed to the Collator E-Mail address. 
     At 105, 106, 107 and 108 assuming remote user completes the survey, the Respondent processes the SVQ via the following steps: 
     1. Executes the SVQ which reads itself and presents the questions to the remote user, storing the remote users answers in SVQ itself. 
     2. Builds the Survey Response Document (SVR) from information contained within the SVQ. 
     3. Using the Collator&#39;s Mail address information it activates the MS Mail transport to send Mail messages with the attached SVR. 
     At 110 and 111 the Collator processes the SVR via the following steps: 
     1. Reads and processes the Survey Response Document (SVR). 
     2. Checks that the answer is still valid for a current survey--i.e., that the associated survey exists in the Collator&#39;s register. 
     3. Assuming its still valid Collator updates (or inserts) the database fields with the appropriate answers extracted from each of the Question sections of the SVR. 
     4. Deletes the SVR and the associated message from the Mail queue. 
     5. After a certain number or percentage of returned answers, the operator will be alerted and may choose to terminate the survey by setting its status in the Collator&#39;s register. After this SVR&#39;s for this particular survey will be deleted after being identified rather than being fully processed. 
     6. Other features exist such as Collator sending reminders to non-responding Recipients and also resending the complete SVQ again if it has been lost by a Respondent. 
     Rules 
     1. When a new Question Box is added to the Survey Document it is created with an area at the top for the question text, and two buttons at the bottom labelled `Next` and `Previous`. These 3 user interface controls are regarded by the design of the Survey Document as non-active as they contain no operator selectable answers, or database field definition information. 
     2. Once a new Question Box is created n the Author module it is assigned a type of `DLG-TYPE-BASE` which is a combination of DLG-TYPE QUESTIONTEXT and DLG-TYPE-NEXTPREVBUTTONS. 
     3. Once a new Question Box is created in the Author module with the type of `DLG-TYPE-BASE` it can become any of the active or complex TPEs, however once one control is added, the Question Box becomes the TYPE of the first active/complex control. If another control type is added the question type will reflect that. 
     4. When a new Survey Document is created by the Author module it is made with a terminating Question Box labelled `(FINISH)`. This varies from the normal Question Box created in the Survey Document, in that it has only one button at the bottom of the Question Box. This button is labelled `Finish`. 
     5. The Survey Document master SVM is the only version of the Survey which can be edited. 
     6. The table creation mechanism will not allow two tables with the same name to be created within a database. If a Survey Master Document is E-Mailed again it must first specify another tablename. This safeguards the integrity of the distributed survey. 
     7. Through the Collator, an operator may set the cut-off point based on the number or percentage of Recipient&#39;s Survey Document answers SVR that it wishes to process. At this point the Collator will automatically set the status of this particular survey to `suspended`. Additional answer documents for this survey will remain in the `in-tray` after this point has been reached in case the operator wishes to extend their chosen cut-off point. 
     8. Through the Collator an operator may terminate a survey by setting its status to `terminated` in the Collator&#39;s internal register. As soon as the survey is terminated any answer documents for this survey will be erased by the Collator module. 
     `Branching Control Language` (BCL) 
     An embodiment may utilise &#34;branching control language&#34; to control branching between questions in the Survey Document. This is accessed through any given question box&#39;s property dialogue and stored in the `Next` button&#39;s ControlData structure. The `Next` button can either: 
     Be loaded with the RefName of the next Question Box to branch to. 
     Cause (in the case of option buttons) the RefName of the next Question Box to be loaded from the selected Option Button&#39;s ControlData structure. 
     Cause, if the GotoScript is not null, the GotoScript to read and run to compute the RefName of the next Question. Note if the GotoScript is present it will override any other goto logic that may have been implemented by the Author&#39;s operator. 
     The BCL allows two methods to access information from which to make branching decisions: 
     Through the DataBaseFieldName which is uniquely named across the whole Survey Document. 
     Through the ItemLabel field which is uniquely named within its Question Box. 
     The status of any control in any Question Box, or, the selected value of any database field can be interrogated by the language. 
     This script has a fairly simple syntax: 
     
         ______________________________________
IF        Questions(question reference) . `item-label` =/&lt;&gt;
          condition
AND       Questions(question reference) . `item-label` =/&lt;&gt;
          condition
OR        Questions(question reference) . `item-label` =/&lt;&gt;
          condition
THEN        GOTO (specific question reference)
ELSE        GOTO (specific question reference)
ENDIF
or:
IF        Database(`Database Field Name` =/&lt;&gt; value
AND       Database(`Database Field Name` =/&lt;&gt; value
OR        Database(`Database Field Name` =/&lt;&gt; value
THEN        GOTO (specific question reference)
ELSE        GOTO (specific question reference)
ENDIF
______________________________________
 
    
     Where the AND/OR/ELSE sections are optional. 
     Where `=` represents equal to, and `&lt;&gt;` represents not equal to. 
     Where `condition` is either `True/Selected/On/Checked` or `False/UnSelected/Off/UnChecked`. 
     Where `value` is one of the possible values that the specific database field can be set to. 
     Both the selection status and the selected value syntaxes can be mixed together: 
     
         ______________________________________
IF        Questions(question reference) .  item-label` =/&lt;&gt;
          condition
AND       Database(`Database Field Name` =/&lt;&gt; value
THEN      GOTO (specific question reference)
ENDIF
______________________________________
 
    
     At least the preferred embodiment enables formulation by the local user of a Survey Document which incorporates complex branching pathways between questions. 
     Generally, any question may include a branch to any other question in the document, depending on document structure design. There may be any number of complex pathways through the document, any of which may be followed by the remote user, depending upon his given answers. 
     The rule is that a question cannot refer to a preciously answered question, but can branch to all others. A branch can be triggered by any preceding answer or answers. 
     It will be appreciated that the present invention may vary from the specific features of the embodiment disclosed above. The invention has wide commercial application for information gathering purposes. It enables a use to ask any type of questions, any number of questions with any branching complexity, of hundreds or even thousands of users. Responses are automatically processed, the pertinent information extracted and loaded into an appropriate place in a database which is automatically constructed for the local user. The user can then analyse the information any way the he likes. 
     It will be appreciated by persons skilled in the art that numerous variations and/or modifications may be made to the invention as shown in the specific embodiments without departing from the spirit or scope of the invention as broadly described. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive. ##SPC1##