While this process resembles the 'Interview' features found in other programs, it really is not. Interview forms used in competitive programs require quite intricate and oftentimes complex setups:

In most programs, the 'results' connections is accomplished via exercises that result in complex commands that are inserted as fields either in the base document or most likely in a separate file.  Then you have to lock in the form as save it out to a special location under a special name with a special suffix.

   Pathagoras does not require that kind of programming from its customers. Pathagoras Interviews are created directly from the assembled document. They are "dynamic" and created "fresh" each time you run the program. That mean that if you change the <<*Option/Optional*>> text block in a source document and then assemble a new document, the change in the source will reflect the next time the Interview Wizard is run on the subsequently generated document. This makes testing the document, and the resulting Interview, exceptionally easy, and fully understandable.

   Of course, when you are inserting and editing <<*Options*>> and <<*Optional*>> blocks, and creating your If/Then and and Case equations, you are 'programming' in a fashion . But it is quite different from what is described above. Pathagoras 'programming' is 'facial' to the document, and not independent from it. By facial, we mean that just by looking at the document's face, you can see what is happening.  When something doesn't happen as expected, the face of the document 'tells' you why.

   Plus, since each Wizard is created dynamically by Pathagoras, you don't have to create a special form. All you have to do is properly set up the various <<*Options*>> and <<*Optional*>> blocks in the source text. If you encounter errors in the processing, or just want to make changes to rewrite a question or correct a logic issue, simply work on, and then save, the source document. The next time you run the Wizard, it will show a new Interview reflecting your changes. (If the document has  <<*Options*>> and <<*Optional*>> blocks that are (or may be) improperly formed, run the "Structure Checker." Pathagoras will typically detect and fix any formation or structure errors, or at a minimum will point out the section of the document that contains the likely source of the error.)