Re: Problems with INPUT statement

Spokey the Wheeler <spokey@haunted.demon.co.uk> wrote: >But if you're just trying to get the user to enter lots of text, I'd far >rather use a detail table which joined on the primary key of the main table >and had a line number. That way you don't have waste 991 bytes on every >record! :-) Ahem......... Not to say this way won't work or isn't good (Fourgen did theirs that way FWIW), but there is another option I must submit. First, use a VARCHAR on the field in the header if possible. If not, OK. Second, you can set up an "array" of form fields e.g.: [f001 ...] [f001 ...] . . . [f001 ...] Make these fields as wide as needed, preferably the same length which is divisible into 1000. Twenty lines of 50 characters would be a good choice. In your attributes section: f001 = patient.notes, WORDWRAP, COMPRESS; This will create a word-wrapped entry field for the whole field, and will compress it into a single string (no line breaks). The user can enter/edit the field in a very simple text-editor environment using the normal 4GL input editing commands. I may have some syntax wrong, but I know the concept works. In any case, there are advantages and disadvantages to both methods. Use the one which your version supports, and your database requirements demand. Cheers. Mike Lemon