The following new message has been posted on Phorm Support Forum at <http://www.phorm.com/support/>. *************************************************************************** MESSAGE: (#4500) Re: White space trim or retain optionable ? <http://www.phorm.com/support/?rev=4500> AUTHOR: Joseph Maxwell DATE: November 30, 2004 at 10:39 a.m. EST Reply To: (#4484) Re: White space trim or retain optionable ? Author: Holotech Date: November 25, 2004 at 8:58 a.m. EST The same data is in the log file Ex: From a text input ==> "44AllStateDr" instead of "44 AllState Dr" From a textarea input ==> "...Technicalandotherconsultingservices....." instead of "... Technical and other consulting services ....." The Phorm Processing uses a "|" for field delimiter ==> $PHORM_LDELIM = " | "; Which raises another question, in passing the data to the MySQL Database, the "|" is not recognized as the delimiter and all the data is displaced into one column of the table. I needed to log data to both MySQL for permanent storage and to a more volatile flatfile for less formal manipulation by a script. What would be a smooth strategy to get MySQL to accept "|" > My guess is that the problem is with displaying the > data: anything more than a single space is ignored > when displaying data in a browser. Have you looked > directly at the log to see what data is there? *************************************************************************** This is an automatically-generated notice. If you'd like to be removed from the mailing list, please visit Phorm Support Forum at <http://www.phorm.com/support/>, or send your request to webbbs@xxxxxxxxxx If you wish to respond to this message, please post your response directly to the board. Thank you! ------------------------------------------------- You are receiving this message because you are subscribed to the Phorm mailing list. To send messages to the mailing list, simply send email to phorm@xxxxxxxxxxxxx from the address you have subscribed. You may unsubscribe from the list by sending email to phorm-request@xxxxxxxxxxxxx with 'unsubscribe' in the SUBJECT field.