Re: Input --- for the "Why Not?" Dept.
Posted in 1997
Topics: Stored Procedures & SPL, Connectivity: ESQL/C, 4GL & Embedded SQL, Data Types & Schema Design
Andrey J. Geydan wrote: > > > gets truncated on the screen, but the real data is OK. > > > > My problem arose when the users decided they need to free-type into one of > > these fields. The screen has no more room for more lines, and the field is > > only 40 characters displayed. The user nees 255 characters!!! > > > > The field is defined as: > > { > > Detail: [a27 ] > > } > > table > > x > > attributes > > a27 = x.detail > > > > Table x defines detail as Varchar(255,1). > > > > When the user is entering data into teh Detail line, Informix cuts them off > > at the end of the line. How can I get Informix to continue entering on a > > "scrolling" line? > > > > I guess the "Why Not" comes into play because what I need is done by Informix > > in "Construct" statements! If they built that ability into Construct, why not > > include it in Input??? > > > > Try AFP Informix 4GL at qws.msk.su. It's allows scroll forms, > scroll fields, bar-menu and so on... I use this, nice think. > > WBR, > Andrey Geydan. > > --- > Andrey Geydan. > Computer group manager. > Pardaugava 'D Ltd. > Phone +371-54-22672 Isn't there a "scroll" attribute you have to put in ".per" defination ? I have done a scrolling text but I am SURE that it is given in one of the manuals.