Well, the default delimeter for the getline function is the newline character, meaning that it would read all the characters up to (but not including) the newline. This is what your initial call to getline did. In the loop, it would keep reading lines from the file and placing it into the string, Full_Data. Note that this did not append to Full_Data; after each iteration, Full_Data just contained the next line. In your original code, assuming it found the file, Full_Data would contain every character between the last newline and the end of file character at the end of the loop.
The end of file character (ascii 26) is placed automagically at the end of each file. Putting that as the delimeter in getline would make it read the whole file at once and place it in Full_Data, which is what you wanted.
I find it a bit odd that the above code works for Janlan, specifically because of the single backslash in the file paths. The reason this is an issue is, for instance, take the string "C:\news\tabloids\007". If you outputted it you would get the following:
C:
ews (horizontal tab) abloids |
because of the special characters '\n', '\t', and '\0'. You need to escape the backslash (unless of course you want the effect as above). I guess certain compilers parse strings differently.