> JS> No more quick'n'dirty functions for me.  It really threw me when
 > JS> the problem manifested itself differently when I removed the
 > JS> array and made it a single record.

 > It is a bit of a bugger.  I've had the same problem when
 > using cin.  After using a cin.get(char*,int,int) I've found
 > it is necessary to do a cin.get() after _every_ cin call.

Then use istream::getline(), where the '\n' is automatically discarded, or
better yet, define a string class which allows you to accept and parse the
precise object you're looking for.  There's little point in using an OOP
language unless you're going to follow the same philosophy.

---