jwcolby
jwcolby at colbyconsulting.com
Fri May 4 08:59:50 CDT 2012
The two bytes are probably a CR (carriage return) and a LF (line feed). You can do a replace with vbCR and vbLF or maybe even vbCRLF. These characters are not visible in the normal sense. You can probably treat the string as an array and try and get the char() value of each byte. You would have to look at a table of ASCII to discover what the CR and LF characters are, I know they are down in the teens 0x15 perhaps? John W. Colby Colby Consulting Reality is what refuses to go away when you do not believe in it On 5/3/2012 5:43 PM, Brad Marks wrote: > All, > > We have an Access 2007 application that reads data from a Firebird > database via ODBC. > > There is a field that appears to be spaces but it is not spaces. We did > a "trim" and it went from 10 bytes to 2. > > We have tested for spaces and it appears that the two bytes are > something other than spaces. > > We would like to see what is in these two bytes. > > In a prior life (IBM Mainframe) we had utilities to "view in Hex". > > Is there anything like this for Access? > > Thanks, > Brad >