Well, there is encryption, but that doesn't prevent the file from being modified (or deleted).
Is the information "static", i.e. the file is Read-Only, and will never be changed (unless you change the Main Routine)? If so, you could take the information within the file and write a "Constant VI" (Write-Only) that you build as part of your executable. Note that you might still have a "visibility" problem, since if your customer were to view your executable with a Text Editor, and you had such a Constant VI whose content was text, it would probably show up in the Editor.
What is in the file? If it is an XML file that lists configuration variables (like a .INI file), you would write a small utility that reads the file, extracts the XML variables to their "native" state (which I'm guessing is largely numeric), and writes a Binary file, which is the file you provide to your customer. In your code, you have a Develop/Deploy choice (perhaps using Diagram Disable) -- in Develop, you read the XML file (on your own PC), but you hand the customer the executable in Deploy mode, where you replace the XML Reads with a Read of the Binary file, reading into the same set of variables. Your utility would create the Binary from the XML, of course ...
Those are just some ideas.
Bob Schor
