walt@sixwbn.UUCP (Walt Novinger) (02/27/89)
A friend needs a method to protect a sensitive database from his employees and others. He's using FileMaker II, and wants the following capabilities: 1) Limit the ability to print database records to only those individuals who have the password necessary to activate the printing function. This would probably be some installed(able) function of FileMaker II. 2) Have the ability to somehow protect a file on the hard disk from being copied to floppies. I have already tried setting the "No Copy" attribute (using DiskTools II) -- this doesn't seem to do the trick, as the file can still be dragged to a floppy. If any netters out there have suggestions for ways to protect database information (short of switching to another database program (:)), we'd be happy to hear about them. Please email to the return address -- if there's sufficient response, I'll summarize and post the results. =============================================================================== Walt Novinger | ...!sun!plx!walt | Plexus Computers, Inc. | ...!sun!sgi!sixwbn!walt | No more goodness can be 3833 N. First St. |------------------------------| attempted than the San Jose, CA 95134 | Disclaimer: You mean my | people can bear. 408-943-2406 (w) | boss might read this? | Thomas Jefferson 415-964-9377 (h) | Nah - he forgot his password!| ===============================================================================
md32+@andrew.cmu.edu (Michael Joseph Darweesh) (03/01/89)
Keep your data on a floppy. If you are really paranoid, put the floppy in a strongbox. The Weesh Carnegie Mellon md32@andrew.cmu.edu md32@andrew.bitnet