Thank you, Yes, I am still encountering problems. The 32 K is a problem I have tried to create workaround splitting the total field up in portions of about 30 K. This works fine when the total length is less than about 50 K, but it does not work aymore when the field is about 80 K Then I am already getting problems to calculate the length of the field using SLEN, sometimes it works sometimes there is an error message about a lack of resources.
So I am still looking for a solution and already have put a question to the dream team. Tony -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mike Byerley Sent: woensdag 22 mei 2013 18:57 To: RBASE-L Mailing List Subject: [RBASE-L] - Re: maximum size of VARCHAR variable limited to 32KB? It might be a 32k limitation. ISTR we were getting SRPL (as well as the other string function) to work on Varchar in about the same timeframe as DLCall. ----- Original Message ----- From: "Albert Berry" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Wednesday, May 22, 2013 11:21 AM Subject: [RBASE-L] - Re: maximum size of VARCHAR variable limited to 32KB? : It seems to me that the string is too long for the SRPL function, but : the help doesn't specify a maximum length. Try asking RBTI for help. : They are usually very, very good at giving a hand : : Albert : : On 21/05/2013 12:41 PM, Tony IJntema wrote: : > It looks like this is the answer. : > But now I am confronted with an error message : > : > Details are: length of the variable is 41346 bytes : > : > I try to perform a search - replace like: : > : > SET VAR V_tekst = (SRPL(.V_tekst,'E','X',0)) : > : > The result is: : > : > ERROR- Insufficient buffer space to process expressions. (2136) : > : > Is there a setting which I can change? : > : :
