Thanks Simon I'm an idiot - dev environment was running as admin - so nothing else could write to DB out side of this as a normal users.
Paul www.sandersonforensics.com skype: r3scue193 twitter: @sandersonforens Tel +44 (0)1326 572786 http://sandersonforensics.com/forum/content.php?195-SQLite-Forensic-Toolkit -Forensic Toolkit for SQLite email from a work address for a fully functional demo licence On 7 March 2015 at 17:56, Simon Slavin <slavins at bigfraud.org> wrote: > > On 7 Mar 2015, at 4:42pm, Paul Sanderson <sandersonforensics at gmail.com> > wrote: > >> I have a database I have created and populated with various tables and data. >> >> I now want to create a new table and I get the above error. >> >> command is create table testtab (id int, data blob); > > If you are not already doing so, try using the SQLite shell tool to execute > that command and see if you get the same error. > > The database may be read-only for several reasons. You can explicitly ask > SQLite to open it read-only. The file may be marked for read-only access for > your user. The folder may be marked for read-only access, which would > prevent SQLite from creating a journal file for changes. And several other > causes. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
