I just commented on a post recently wondering why programmers still suppress errors on functions they are trying to debug. To all who may read this post, in the words of the Waterboy's mama, the "at sign" @ "is the devil!!!!" If you have @ characters in your code while debugging take them all out now! You need to see the errors, not suppress them. Okay stepping off my soapbox...
Change...
@mysql_query($sQuery);
...to...
mysql_query($sQuery) or die('A database error occurred: ' . mysql_error());
That will ensure that you can now at least see what error is returning. Post that here. However, if you are using the 'theimportwar' user in your mysql_connect() then I suspect you will just get the same error as phpMyAdmin (which basically states that you do not have permission to either select from the database you are using or the user that php is being ran under doesn't have write permissions to that path.)
If you can select from that database but not do a "INTO OUTFILE" than I suggest creating that file from the command line (unless it's there already):
$ touch /var/www/html/myText.txt
Then change permissions if you can:
$ chmod 666 /var/www/html/myText.txt
If that doesn't work, you'll need to chat with the administrator.
Now, if you have problems as mentioned above, you can simply query the table with php and print out the results dynamically instead of creating a file each time (in fact, 9 out of 10 times this is how it's done.) Look at this article.