|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Let's say the field is 32,000 bytes. How would you do that? I still say the html text keyword kicks a$$ for this kind of field? Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin Vern Hamberg <vhamberg@centerfieldtechnology.com> Sent by: midrange-l-admin@midrange.com 12/20/2002 10:12 AM Please respond to midrange-l To: midrange-l@midrange.com cc: Fax to: Subject: Re: QDOC exceeded storage size Rob What are the hoops? IIRC, you define a single large field, it wraps in the space you give it. I know many used to use a subfile or multiple fields for this, but the single large field works fine in DDS. What am I missing? Cheers Vern At 03:33 PM 12/19/02 -0500, you wrote: >This is a multipart message in MIME format. >-- >[ Picked text/plain from multipart/alternative ] >With variable length fields and whatnot why use postgresql vs DB2/400? > >I sure wouldn't use 5250 for data entry into this though. We've migrated >some applications from OV/400 into 5250 data entry. The hoops that you >have to go through to do a window for large text entry are pathetic >compared to one line of html - (text). > >Rob Berendt >-- _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.