Re: Printer escape sequences in SE table
Posted in 1999
Topics: General Discussion
I believe you are hitting a problem I had before. The Informix DB only stores "some" control characters in a table (except for the super duper 9.x versions). Your "control" character is being converted to a space when stored... Why not change your field to char(8 or so) and store the code without the backslash... LET xstr = "\\", table.compresscode PRINT xstr CLIPPED, "THIS IS COMPRESSED, I HOPE" Steve -- Steven L Cooper Manager, Systems Engineering --------------------------------------- Please reply to NG only, so others may be enlightened... The views expressed here are mine and you can't have them...unless you agree! Scott_Gallup <Scott_Gallup@email.msn.com> wrote in article <eMj0EckP#GA.268@upnetnews02.moswest.msn.net>... > I would like to set up a table that contains the escape sequences for > compressed printer, etc for different printers. When I do this and select an > escape sequence from the table and attempt to print using it I get the > literal string, i.e. \\033&k2s (which is exactly what is in the table - the > column is defined as a char). > > If I assign the string to a char variable in the program i.e., LET xstr = > "\\033&k2S" and then print using this variable ( PRINT xstr CLIPPED, "THIS IS > COMPRESSED") then the text string is printed in compressed format. > > I also tried setting the value in the column to \\\\033&k2S (attempting to > escape the escape character) but this didnot work either. > > I know I've seen this done where it works, and believe that several years > ago I did this. But for the life of me I cannot recall how. Anyone have any > ideas and/or suggestions. > > Thanks in advance. > > Scott G. Gallup > Information Services Manager > Belle Tire Distributors > Allen Park MI > Scott_Gallup@msn.com > > >
Steven L Cooper wrote: > I believe you are hitting a problem I had before. The Informix DB only > stores "some" control characters in a table (except for the super duper 9.x > versions). Your "control" character is being converted to a space when > stored... Hmmm, this shouldn't be true, at least not on any version of Informix DB I've seen (meaning the last 7 years). There *were* some issues on different versions (early 4 or 5, and the early releases of GLS on 7.2) where inserting the Ascii values above 127 (national characters) was rejected, but never turning them into spaces. That would be a major bug. June -- june_t@hotmail.com Grounded in Palo Alto, living on animal crackers