home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.databases.paradox      To crash or not to crash, asks Borland      9,834 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 9,255 of 9,834   
   Jim Hargan to Anne Wainwright   
   Re: importing large data fields   
   14 Jun 08 19:26:58   
   
   From: contact@harganonline.com   
      
   Hi Anne!   
      
   I can't address the import routines (interactive or OPAL, which has an   
   entire datatype devoted to them); I've found them so powerful that I've   
   never run up any of their limits! But evidently you have.   
      
   Fortunately, you also have the textStream type. When I first read the OPAL   
   help on it I thought there had to be a catch; nothing is this simple. I   
   found out that, yes, it really is that simple.   
      
   TextStream methods read and write text files. If your source is any sort of   
   text file, you can use textStream methods to read it into string variables,   
   one line at a time. String variables since v7-32 (I think) have no limit on   
   size -- none at all. You can cram /War and Peace/ into a single string   
   variable if you want. Then you write it into a memo field:   
   myMemoField'value = stWarAndPeace.   
      
   How you do this depends on the way your source is formatted. If your source   
   uses a field delimiter that does not appear within the fields, then it's   
   easy -- use textstream to read each line of the source into a string   
   variable, then use breakApart on the delimiter. For CSV, advMatch on   
   ..\\",\\".. suggests itself, although I've never tried it myself.   
      
   HTH   
      
   Jim Hargan   
      
   On Sun, 15 Jun 2008 00:39:24 +0200, Anne Wainwright wrote:   
      
   > hello, me again.   
   >   
   > I am importing data larger than 256 chars per field, but cannot import   
   > into a memo fieldit seems.   
   >   
   > Conversely, if I have a memo field then when i export to a separated   
   > format then only the first 256 chars get out.   
   >   
   > These seem to be the basic limitations in the interactive mode. I haven't   
   > looked at it in great detail, but are there ways around this without   
   > clever code (or even with it)?   
   >   
   > Thanks for any comments.   
   > Please reply to newsgroup only.   
   >   
   > Anne   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca