Hi,
Apple's port of GCC is sort of funky and you're not the only one I've heard having problems with it. If you don't fix it, I suggest building GCC from source. Don't worry, it's an easy process.
First of all, make sure that file.h is there and that both spellings are correct! You've probably done that already but I mentioned that anyway. Many times, people just make silly mistakes. It happens to everyone.
You were pretty vague about #include "file.h" - does it work or do you just think it works? Have you tried it? Unfortunately, the use of #include "file.h" is usually discouraged because different compilers vendors implement it in different manners; it's not standardized.
Try using the -include file.h argument and see where that leads you. Also, try shoving file.h in the same directories as all your other standard header files.
IMPORTANT NOTE: The previous answer is wrong in that inverted commas are not supposed to work differently on non-standard include files, as per the ISO C++ standard.
Cheers,
Bogdan