From: Michael Vealey <[log in to unmask]>
Subject: Help! Invalid ASCII digit errors in native mode
 
We are migrating piecemeal to native mode. So far, we haven't had
many major problems (knock on simulated woodgrain laminate) but the
one that's taking the largest chunks out of our posteriors is invalid
ASCII digit errors.
 
It seems that when we get a not found condition on a DBGET, random
garbage is left in the record space. This is understandable but our
old classic didn't seem to mind. The new box is giving us fits! All
the programs running in compatibality mode handle this just fine but
kick it up to native mode and WHAM!
 
To date, our solution is to initialize the record space after an
unsuccessful DBGET. Is there a simpler answer?
 
 ==============================================================================
=
Michael A. Vealey                       = We will conserve only what we love.
University Computing Services           = We will love only what we understand.
University of Maryland Baltimore County = We will understand only what we are
[log in to unmask]        =                        taught.
 ==============================================================================
=
 * All opinions expressed are mine and mine alone. You can't have 'em. Nyah! *