You could try obfuscation - that is, using nonsense strings that can be mapped to the real table/column names by your program.
You could add a password to the database, something built into the software so that users wouldn't even be able to open the database. On Fri, Feb 12, 2010 at 10:54 PM, Tushar Kale <[email protected]> wrote: > > Hi Charlie: > > Thanks for the quick response! > I think I can use the encrypt=true flag when database is created. This will > prevent user from opening the database files in OS and dumping them to see > data. Somehow I need to protect the data structures (tables/relationships > etc) in the database. -- Family photographs are a critical legacy for ourselves and our descendants. Protect that legacy with a digital backup and recovery plan. Join the photo preservation advocacy Facebook group: http://www.facebook.com/home.php?ref=logo#/group.php?gid=148274709288
