Yep, using ExpandFilename prints out the full path of where I expect the file to be '/home/cyberfilth/Development/Nergal/nergalConf.xml'And ls /home/cyberfilth/Development/Nergal/nergalConf.xml actually confirms the file is there?
Whether the filename exists or not shouldn't matter.
And ls /home/cyberfilth/Development/Nergal/nergalConf.xml actually confirms the file is there?It isn't there the first time the application runs (and it gives an error), it is there the second time the application runs (and still gives the error)
Whether the filename exists or not shouldn't matter.Let me clarify that, FileExists should just evaluate whether the file exists or not. The application then responds as required.
Let me clarify that, FileExists should just evaluate whether the file exists or not. The application then responds as required.
What's happening now is, the application checks if a file exists, then regardless whether it does or not, it's producing an error message, then continuing on as normal. So it is correctly evaluating whether the file exists or not, it's just halting program execution and showing an error when doing so.