Hi Joe, Adding two extra backslashes worked a treat. Many thanks for replying. Would never have occurred to me to try that. No other Windows program uses that convention, so seems 'alien' to me.
Again, thanks! Chris On Thu, May 26, 2016 at 6:17 PM, Chris Locke <ch...@chrisjlocke.co.uk> wrote: > Aah, thats handy. Will try that. Thanks for that - much appreciated. :-) > > Thanks, > Chris > > On Thu, May 26, 2016 at 5:38 PM, Joe Mistachkin <sql...@mistachkin.com> > wrote: > >> >> Chris Locke wrote: >> > >> > Have used system.data.sqlite.dll (1.0.67.1) for ages with no problems. >> > Recently thought, "wonder if there is a new version?" but on using it >> > (1.0.101.0), I can't access a database remotely - comes up with "unable >> to >> > open database file". DB Browser for Sqlite opens it fine, so its not >> > corrupt. In fact, if I go back to 1.0.67.1, it opens fine. >> > >> > Wondered if this was either 'by design' (something added since .67) or >> > something I was doing wrong?! >> > >> >> Due to the revised connection string parsing algorithm (which was revised >> to fix other issues), opening a database on a UNC path requires that the >> initial backslashes in the file name be doubled, e.g.: >> >> \\\\mypc\db\Mydb.db >> >> -- >> Joe Mistachkin >> >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@mailinglists.sqlite.org >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >> > > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
