SQLite has no knowledge of users or password protection. Unlike MSSQL or MySQL or Oracle, you don't log into the database with a username and password, and there is no real DBMS to handle permissions. Filesystem level locking is pretty much the closest thing you're going to get to protecting the data within.
I'd suggest encryption to at least block people from getting access to the file content, however, once the encryption is broken, R/W access will be permitted. If you want a total "black box" scenario, this is probably going to be your best bet. If you want to block write access, you could create a new user account, give RW permissions to that user, then give just R access to everyone else. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users