After reading some other posts, I think I may have been under an incorrect assumption. Hopefully, somebody can help clarify it for me.
The original concept I was working under was that if I embedded SQLCE into my application, it would be part of the .exe file that is created and I would be able to access that database while it is still in the .exe file (and the end-user wouldn't have any access to that database, other than through the UI).
Now, it appears that although the database itself is, indeed, embedded inside the .exe file, the only way to use the database is to write it to disk. And, if any changes are made to the database, those changes can't be written back to the database within the .exe file.
Am I correct in my "new" assumption? If I want to 'hide' the database from the user, what are my options? So far, I've come up with:
1. Using a password on the database.
2. Encrypting the database.
Are there any others that might work for me?