> The statement file.createNewFile() fails on a read only share. Since
> the file is there it should be possible to access it.
That's interesting, the Java spec I was following states that createNewFile():
"Atomically creates a new, empty file named by this abstract
pathname if and only if a file with this name does not yet exist."
So if the file exists on the read-only share, the call to
createNewFile() should do nothing and return false, and SQLite will
proceed to open it for reading. Is this not the behaviour your seeing?
If not, try the following:
- if (file.createNewFile()) file.delete();
+ if (!file.exists() && file.createNewFile()) file.delete();
If this works, you've found a bug in the JDK.
d.
--~--~---------~--~----~------------~-------~--~----~
Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en
To unsubscribe, send email to [EMAIL PROTECTED]
-~----------~----~----~----~------~----~------~--~---
