DD>
  >    strcpy(cTest, "12345678901") ;
  >    WinMessageBox(/*...*/ cTest /*...*/) ;
  >
  > No matter what I do it ALWAYS displays the first 3 chars and truncates
  > the rest.
DD>

  If it is *truly* the case that there is no intervening code between
  these two lines, then even heap corruption isn't the answer (unless
  your application is multithreaded), because there is no heap
  mauipulation between the time that the memory pointed to by `cTest' is
  modified, and the time that it is passed to WinMessageBox().

  I suspect that you are a victim of corrupt string literals.

  It may well be that at some point you are writing over the memory that
  contains the string literal "12345678901" at some other point in your
  program, most likely by exceeding the bounds of an array that has
  static storage duration (i.e. that resides in the "data segment"
  rather than on the stack or the heap), or by aliasing a literal to a
  pointer and then modifying the data pointed to.

  One way to check this is to use one of the little-used features of
  many C++ compilers : that of forcing string literals to be grouped
  into a read-only data area.  This will cause the program to be halted
  by OS/2 as soon as something attempts to overwrite those literals.

  Most of the C++ compilers for OS/2 support this in one way or another.
  With MetaWare High C++, for example, you surround the strcpy line by
  `pragma On(Read_Only_Strings);' and `pragma Pop(Read_Only_Strings);'.

  Of course, if the problem *is* that you are overrunning an array with
  static storage duration, rather than pointer aliasing, then moving the
  strings into a read-only area simply means that something else will be
  overwritten instead, in which case it is time to fire up the debugger.

  > JdeBP <
___
 X MegaMail 2.10 #0:

--- Maximus/2 3.00