CHR$(0) thru CHR$(31) in SQL statement

[Easy]

<br>
I work for a company that has numerous Btrieve tables that use CHR$(0) thru CHR$(31) for flags and status of records. Ten years ago it made sense due to the cost of memory (a STRING*1 versus INTEGER*2 {there was no INTEGER*1 back then}).<br>
<br>
Unfortunately, when you submit a SQL statement to the server with a variable equal to NULL (CHR$(0)) the SQL engine truncates the statement at the null and, of course, trips an error.<br>
<br>
PROBLEM: How do I use Chr$(0) thru Chr$(31) as legitimate values for "SELECT" and "INSERT" commands in variables without SQL hiccuping?

 

[MikeLacey]

This might be "teaching my grandmother to suck eggs" (charming english phrase) but have you thought about encoding your data by (for instance) converting the NULL character when it appears into the string "~~chr(0)" or something else unlikely to occur in text data.<br>
<br>
Alternatively you could store that data in a data type intended for binary data. In Oracle that would be "RAW" or "LONG RAW". I can't comment about SQL Server because I use a *proper* database &lt;smile&gt;<br>
<br>
Regards<br>
<br>
Mike<br>