After reading the link that Rick provided, I am not understanding what everyone is saying about this thread.
From the KB: SYMPTOMS After changing the format of a memo field to upper case in the Report Writer, the error "String Too Long to Fit" appears when attempting to print or preview the report. Back to the top CAUSE The Report Writer's expression builder cannot convert fields larger than 256 characters to upper case. You must use the UPPER() function to convert those fields. Back to the top WORKAROUND In the Report Expression box for the field, use the UPPER() function to transform the memo-field contents to upper case. In the designer when you press Format, To Upper it will not convert the memo field to upper case in the designer. It says to use UPPER(field) in the control source as a work around. Everyone in this thread says that VFP should be able to do an UPPER() on a memo field and apparently it does. Am I missing something? Jeff Jeff Johnson [EMAIL PROTECTED] SanDC, Inc. 623-582-0323 Fax 623-869-0675 Phoenix Python User Group - [EMAIL PROTECTED] Rick Schummer wrote: >>> If you're really curious, and not just being defensive about MS<< > > I absolutely was not defensive about MS, and in fact stated about the issue > in the KB article: "I > agree it is a poor design to have a string too long error when you UPPER() a > memo field." > >>> And while your exhaustive explanations may be technically correct, they >>> still leave a bad > impression.<< > > No doubt users hate to hear their alleged bugs are by design. I know, me too. > Yet I have an open > mind when working with all software vendors when they report this back to me. > I also call them on > the carpet when I think their designs are wrong and need to be fixed. Do not > confuse the true > definition of bugs and the real world implementation of the business process > to deal with them. They > are completely different issues. It is also why I stated that small companies > (like most of the > people who frequent this list) can out maneuver the big boys, and be way > better at responding to the > customers' needs including issues reported about the software we create. > >>> Go through these, and see how reports are handled. If you find a case > of either Paul or me being dismissive about a report, please point it out.<< > > Really don't have the time to handle this request. I am having too much fun > working on VFP projects > at the moment, securing new projects, and growing my business. Knowing what I > know about you two, I > am sure you guys handle the reports with nothing but the best intentions of > the Dabo developer base. > > Rick > White Light Computing, Inc. > > www.whitelightcomputing.com > www.swfox.net > www.rickschummer.com > > > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
