Timo wrote: > OperationalError: unable to open database file Note that there is a group specifically for using Python with SQLite:
http://groups.google.com/group/python-sqlite Unfortunately SQLite's error reporting isn't particularly detailed when opening databases. There are a lot of things that have to happen beyond just opening the database file. For example the journal needs to be checked for, applied and deleted if present. Windows especially has issues with tag alongs - other programs like virus checkers, backup applications, TortoiseSVN etc that track file activity and then grovel in the files. These can prevent the programs actually using the files from doing things like deleting them (the tag along has the file held open). SQLite does have code to retry some number of times hoping the tag along has finished, but if the system has enough of these installed it may not be sufficient. Note that tag alongs may not be the cause, but rather an example of behaviour similar to what you are seeing. Ultimately you'll need to take an inventory of the machines looking for what is common and what is different. If you can reproduce the problem then use Process Monitor from Sysinternals to see what programs are accessing the file/directory and what error codes are being returned. Roger _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
