Re: A call to arms!

In article <1993Feb11.235131.7284@mnemosyne.cs.du.edu> aburt@mnemosyne.cs.du.edu (Andrew Burt) writes: >We're in the middle of negotiating with Informix to provide an >adequate work-around for error -4518. Mainly, we have a fairly complex >chunk of code, reports which need wordwrap, clipped, print using, and >so on-- basically finding about every way one can trip -4518 ("out of >temporary string space"). The workarounds are (a) not satisfactory (we >*need* the formatting) and (b) not sufficient -- even with *all* the >workarounds in place, we still get it. Strange as it may be, but this error does not crop up in RDS 4.0. Mind you 4.0 has it own set of problems, but not the -4518. I only see this when I port code to a 4.1 RDS. On one system, I have RDS 4.0 running against a Online 4.1 environment. All my 4GL code (and it's complicted stuff, I've written in 4GL since the day it came out) is working just find. One little curiousity that did pop up and have found a work around, is in a function call I might do something like: DEFINE ms CHAR(80) LET ms = column 1, "junk1" column 40, "junk2" column 70, "junk3" Well, instead of junk3 starting in column 70, it'll start in column 66. I'm not exactly sure of the problem, but if define ms as char(132), the problem disappears. Except if I try to print in a column over 80. This is solved by defining ms as char(265). Essentially, double 132+1. I don't have any more problems. Since doing this, I haven't seen any more formatting or -4518 errors. It works for me. Who knows, it might work for you. >-- > >Andrew Burt aburt@du.edu > >"But if he was dying he wouldn't bother to carve "Aaaaargh", he'd just say it." -- "The best government of all is that government which governs the least." Jefferson Brian Douglass briand@anasazi.com 602-870-3330 X657