Search results

Yes. If I do that, even the <CR><LF> characters get ignored. I will prototype the following approach: 1. When a record becomes the current record, convert all <tab> chars to 3 spaces and set 'dirty' to false 2. Allow spaces to be inserted; if any change is made to the field, set dirty to true...

I have an Access 2010 system that stores program source code. (PostScript, but that is not relevant to this problem) in a table as a memo field. It works fine except that forms showing the source code donn't deal with tab chars by indenting, as one would expect. <CR> and <LF> are fine. But not...