bochner@lange.harvard.EDU (Harry Bochner) (09/17/90)
How do you handle a character field that's too long for the screen in 4gl? What I want is to split the field into 2 screen fields, so that the second acts as a continuation of the first. Perform handles this pretty nicely: you can say f1 = tab.str[1,78]; f2 = tab.str[79,156]; and it does what you want, i.e. it maps the 2 screen fields onto one database column. I just had my first occasion to use this technique in 4GL, and am dismayed to find that it doesn't work, at least not in version 2.10.03F. (I'm _still_ waiting for version 4.0!) The suggestion on page 3-16 of the reference manual does make much sense to me, but I tried it, and it doesn't seem to work. Am I missing something? or has any one figured an alternative approach? Harry Bochner bochner@das.harvard.edu