Re: Problems with null in a report with Informix-4GL

This is because 4GL is based on C and uses the strange C idea of a 0 byte as a terminator for a string. It doesn't change your 0 byte to a blank. It stops printing when it finds the null byte. Anyting after that is not printed at all. Unfortunately some printer manufacturers got the great idea of requiring a 0 byte as part of some printer control sequences. What we have done in some cases is to print ascii 128 instead and then written a small unix filter that translates this into a 0 byte. The best route that we use now, is however to print generic printer control codes and then write a little filter that translates these into whatever your particular printer needs. May be I will make it available one day. Don't hold your breath though. On Tue, 03 Feb 1998 16:55:41 +0100, "Evelio Mart'nez" <af.informatica@vlc.servicom.es> wrote: >Hello everyone! > >I am having problems to send a escape sequence that contains a null >character >(let a = ascii 0, ...etc. ) to a report to use it with an HP printer. > >I think it changes it to a blank character. > >Any suggestion will be appreciated. > >Thanks in advance > >Evelio Mart'nez >af.informatica@vlc.servicom.es >