Getting name from user, and handling any errors in C
Nitpick


void retreiveName(char* name)



This should be 

void retrieveName(char* name)


Bugs


        if (name[index] != ' ' &amp;&amp; name[index] != '\0')



What happens if I enter tabs or unprintable characters?  This code would pass a string of all tabs.  Is an all numbers string valid?  

        if (isalpha(name[index]))


Now we check to see if there is a letter rather than excluding only two bad values.  

The &lt;ctype.h&gt; header has this and other functions that you can use.  E.g. 

        if (isprint(name[index]) &amp;&amp; !isspace(name[index]))


This might be what you want if you have a really liberal definition of name.  

Second call

What happens if you call retrieveName twice with the same character array?  In particular, let's give it an input of "Christopher".  


#define BUFFSIZE 10



Christopher has eleven letters, so it overwhelms the buffer size.  That's OK the first time, but the second call would get the remainder of the first call, not a new name.  So the second time you'd be processing the string "r\0ristophe".  That includes a letter, so it will return true.  Not great, since we wanted a new name.  

Now let's change that a bit.  Instead of Christopher, enter "  Chris    ".  Again, that's eleven characters.  It overwhelms the buffer.  The second call results in the string " \0Chris   ".  Now, you 


    for (size_t index = 0; index &lt; BUFFSIZE; ++index) {



When index is 2, it finds a C, which is neither a space nor a null.  So the function returns true on a string that everything else will interpret as " ".  Oops!

And note that this could also happen with two calls that don't overwhelm the buffer.  E.g. the strings "Chris" and " " will call it with " \0ris\0\0\0\0" the second time, assuming the character array was zero-initialized.  

Consider instead 

    for (size_t index = 0; index &lt; BUFFSIZE &amp;&amp; name[index] != '\0'; ++index) {


Then the loop will stop at the end of the buffer or the end of the string, whichever comes first.  

What about other lengths?


bool isThereChars(const char * name)



This only works with one size of buffer.  It would make more sense to allow arbitrary length buffers.  

bool hasLetter(const char * name, int bufferLength)


This allows the caller to specify a buffer length.  

I also like the name hasLetter better than isThereChars.  Your mileage may vary.  Another option is hasAlpha, to match isalpha.  

No need for a flag variable


    bool charCheck = false;
    for (size_t index = 0; index &lt; BUFFSIZE; ++index) {
        if (name[index] != ' ' &amp;&amp; name[index] != '\0')
            charCheck = true;
    }
    return charCheck;



I'd like this better as something like 

    for (size_t index = 0; index &lt; BUFFSIZE &amp;&amp; name[index] != '\0'; ++index) {
        if (isalpha(name[index])) {
            return true;
        }
    }

    return false;


This also has the side effect of returning as soon as you find an alphabetic character rather than processing all the other characters even though they won't change the answer.