I agree with Albert, I wouldn't change it.  Now, if you told me you had a TEXT 
600 (which I have seen in some databases) with everything from 1 character to 
600, then maybe it's worth a discussion.  But 25, heck no!

Happy New Year everyone here on the list!!!

Karen
>From chilly Chicago area (finally winter-like here)

 

 

 

-----Original Message-----
From: Albert <[email protected]>
To: karentellef <[email protected]>
Sent: Wed, Dec 30, 2015 8:38 pm
Subject: [RBASE-L] - Re: Data type


    I would leave them as text, myself. That might be a holdover from    using 
R:Scope to rebuild databases with pointers that have gone out    of whack; 
R:Scope had built in methods of finding like lengths. I    have not needed to 
use R:Scope for so long, relying on frequent    backups instead, that I no 
longer see any benefit to me to purchase    a current copy. As a side comment, 
TEXT datatype saves data in 2    byte increments, so I would look for the 
longest and modify it to    either 24 or 26 as you determine. 
    
    Albert
    
    
On 2015-12-30 5:21 PM, TOM HART wrote:
    
    
      
        
I am          upgrading to Rbase X from 95 so I am doing some much needed       
   changes(for simplicity to myself).  In a table I have been          using 
for years there are several columns that I had defined          as text 25, 
however, the length that is actually entered          varies, sometimes 2 
characters, sometime 20, and so on.  Is it          better to define a column 
like this to a 'note' instead of a          text.  What might be the pros and 
cons.
        
Thanks
        

        
        
Tom Hart
        
        

        
      
    
    
  

Reply via email to