The direct answer to your question is to make an exec call to the command line program 'Attrib'
To hide a file from the system, "Attrib +h <filename>" and to unhide "Attrib -h <filename>".
This process is about as secure as a loonatic deprived of medication.
Using the include media option is enough to thwart most people, but those in the know can go strait past that. Also it bloats your file size. I would love to have more media inclusion options in DBPro.
The best method is to write your own file format, easier would be to scramble a few (or many) bytes of existing files and unscramble them to a temp folder to read them and immediately delete them after reading.
Possibly a better method would be to load media data to a memblock. This in itself might actually be enough to thwart many people if the filenames are suiteably obscure, at least it would thwart non-DB users. You would gain extra security of the files my moving some of the bytes about as that would make it very difficult for even DB users to get at the data.
Note that .bmp, .txt, and .wav are uncompressed formats therefor are extremely easy to crack from a few byte swaps - these files should be more intensely scrambled if you really wish to protect them.
Pneumatic Dryll, Outrageous epic cleric of EQ/Xev
God made the world in 7 days, but we're still waiting for the patch.