O it looks to me like the > 'exclusive' command just needs to be removed ... the threadsafe option that > sqlite3 was built with looks like it is internally handling the locking.
That would be my guess too. -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
