Sharon,

Is this a database that is being processed by RBase for DOS and RBase for 
Windows or at one time was processed by RBase for DOS.  If so the lineend 
character was CHAR(254) to the best of my knowledge.

Jim Bentley

American Celiac Society

[email protected]

tel: 1-504-737-3293

--- On Mon, 3/2/09, Sharon Lima <[email protected]> wrote:
From: Sharon Lima <[email protected]>
Subject: [RBASE-L] - Re: Carriage Return Removal from Text String
To: "RBASE-L Mailing List" <[email protected]>
Date: Monday, March 2, 2009, 12:21 PM

Thanks Buddy for your help.

Why will it work for you and not for me?
There just must be some little something I am doing wrong.

Let's just look at this easier-to-test of the two samples you sent.  
It makes perfect sense to me but I still cannot get it to recall the rows
that have the LINEEND symbol.  I did a copy and paste of your sample below
and got nothing to recall. 

Further information:

1. When I just do an EDIT ALL from the table with no restrictions, of course
the record in question comes up.  Cannot SEE the LINEEND character.
When I double-click select the column with the LINEEND, the text wraps so I
know there is a LINEEND there.

2. VIEW replica of that data behaves the same.

3. However, in VIEW if I force "'s around the text string of the
column with
LINEEND, I can SEE the þ, LINEEND character.  (when recalling ALL rows) 
But I still CANNOT get an EDIT of that record containing the LINEEND using
  EDIT ALL FROM ViewName WHERE ColName CONTAINS (CVAL('LINEEND'))
Or
  EDIT ALL FROM ViewName WHERE ColName CONTAINS 'þ'
Just get <WARNING> No rows exist or satisfy the specified clause.

How can the data be visible (in 3 above) but still not recall with the EDIT
Command?????
I am really stumped.  

Regards,
Sharon

______________________________________________________________________


Sharon
 
  Have you tried 
 
  EDIT ALL FROM TableName WHERE ColName CONTAINS (CVAL('LINEEND'))
 
Buddy
 

________________________________

From: [email protected] on behalf of Sharon Lima
Sent: Sun 3/1/2009 12:56 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Carriage Return Removal from Text String



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