The Factree thread prompted me to fiddle with the templates facility in Gendatam Suite. Horrors - some of the templates did not present properly. This seemed to be a knock-on effect of some other change in the program and fortunately was easily corrected. How about that for informal testing. The Evidence Template facility in Gendatam Suite involves using a mark-up language to define the template and this appears on-screen rather like a computerised paper form. There is a set of 'default' templates programmed in and it is also possible for the user to define their own templates. This latter however involves knowing the mark-up language they use. If you have Gendatam Suite installed look in the FORMS directory for some examples, although as these are blank forms they do not have field definitions. Now, getting to the point, as the templates contain known fields, they can be programmatically integrated so that the relevant records can be automatically generated from the template data. This involves tagging the field definitions in a particular manner through the command parameters. I have found in use that this automatic facility is a bit dangerous. The program may find potential duplicates and will request your guidance. You then have to be extremely careful as any wrong move may be difficult to reverse, particularly if you do not notice until later. I end up taking a series of backup copies of the file just to be on the safe side. So I wondering is any one has any advice in the matter: Is it sensible (a) to let users use a markup language to generate templates for what in effect would be a visual database where they can enter, save, view and edit data. (b) allow them to specify the appropriate tags so that their templates are integrated into the progam and can be used for automatic record generation. Any thoughts welcome, thanks.