Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!jato!herron.uucp!jbrown
From: jbrown@herron.uucp (Jordan Brown)
Newsgroups: comp.databases
Subject: Re: dBase / FoxBase Problem with producing NUL
Message-ID: <320@herron.uucp>
Date: 5 Apr 90 07:18:50 GMT
References: <90093.175401I80QC@CUNYVM.BITNET>
Reply-To: jbrown@jato.jpl.nasa.gov
Lines: 11

Many dBASE variants use C-style strings, which are terminated by
nulls.  CHR(0) is almost meaningless to them.  (Rather, it's almost
equivalent to "".)  Clipper uses length-based strings and can handle
nulls.  I don't know about dBASE IV and FoxPro.

Depending on the application, CHR(128) might be an acceptable substitute.
(If it's going out a 7-bit link to a printer, for instance, 128 will be
trimmed to 0.)
-- 
Jordan Brown
jbrown@jato.jpl.nasa.gov