Jim,

Thanks for your answer.  It gave me a new idea about how to handle my views.


However, I still don’t have this working.  

Although the LINEEND is set to  þ  , nothing is visible when editing the
text field which contains the carriage return.  Also I cannot recall a row
using EDIT ALL FROM TableName WHERE ColName CONTAINS ‘þ’ .

So now the question is, what is the invisible character created by using the
forced carriage return (Shift-Enter) when entering data into the text or
note field?  I need to know what it is that I am replacing with a blank. 

Thanks for any and all help.

Sharon

 

 


Sharon,
Consider creating a single table view that has a SRPL function to replace
imbedid carriage return with another character or spaces (Char(32)). On the
other end if you really need the carriage return you could then replace the
place holding character with a carriage return.  you would export the view
as a CSV 

Jim Bentley
American Celiac Society
[email protected]
tel: 1-504-737-3293

--- On Sat, 2/28/09, Sharon Lima <[email protected]> wrote:

From: Sharon Lima <[email protected]>
Subject: [RBASE-L] - Carriage Return Removal from Text String
To: "RBASE-L Mailing List" <[email protected]>
Date: Saturday, February 28, 2009, 9:50 AM

Hi All,


  


 


  


I am working on exporting data from an R:Base table into a CSV file.  


  


All works well unless a text field has a “carriage return” placed by using


Shift-enter when entering the text data.  


  


It seems to read the carriage return as a comma which separates the fields


incorrectly.  


  


 


  


I tried the following:


  


 


  


UPDATE TableName SET ColumnName = (SRPL(ColumnName,'þ','',0)) 


where þ is my


LINEEND setting.  


  


 


  


This was just a stab in the
 dark and did not work.  Obviously I need some


light on the matter.  


  


Is there anything I can do to remove the “carriage returns” before I do the


export? 


  


 


  


Also, are there any other pitfalls I should know about?


  


 


  


Thanks for your help.


  


 


  


Sharon Lima


  


 


  


 


  


 


  


 


  


  

 

Reply via email to