I all,

I am new to SQLite and I have installed SQLite3 and now I want to connect to the database I have through ODBC, when I tried to install 64bit drivers it is failing with the error:

Error Opening File for writing: C:Program FilesSQLite ODBC driver for Win64sqlite3odbc.dll

any suggestion how to resolve this or to download the correct ODBC drivers?

Thanks Kal

have installed SQLite3

Not sure what you mean since SQLite3 does not have an installation.

32-bit SQLite3.DLL won't connect to 64-bit ODBC driver. You need to use SQLite3.DLL & ODBC driver with matching bitness.

I have SQLite installed(SQLiteStudio-3.2.1) no issues, I can query. My ask is if I want to connect to the tables in SQLite through ODBC from a different application, how can I do that.

I am on Windows 10 , 64bit processor.

I was trying find the correct ODBC drivers and I tried from this link http://www.ch-werner.de/sqliteodbc/ but when I tried to install sqliteodbc_w64.exe, it is failing with the error.

Any suggestion to download and install odbc drivers to connect to SQLite tables?

Thanks

Are you running the .exe with enough privilege to create or write in the "C:\Program Files\SQLite ODBC driver for Win64" directory?

yes, I have write access on C:program files directory

I will pretend that your "I" refers to the sqliteodbc_w64.exe process as you ran it and granted its requested privilege elevation, and that it could then either create its installation directory or alter its content. (If that pretense is false, you have successfully dodged my question and avoided the likely useful implications of a direct answer to it.)

I had no trouble whatsoever running Christian Werner's sqliteodbc_w64.exe program a few minutes ago, and it created the said directory and left a bunch of files there, including the same sqlite3odbc.dll which, apparently, could not be written during your installation attempt. This leads me to think you have some unique, local problem. Perhaps you are already running some process that has loaded that DLL, causing it to not be overwritable. If that is the case, you can either find and stop or kill that process, or rename the DLL to something like "delete_me_soon" and retry your installation.

I do not know what "the correct ODBC drivers" are for SQLite, but I can attest that I have found Mr. Werner's driver to be useful over the years since he began publishing it.

deleted

How will your app help the OP to access a SQLite database via ODBC? As far as I can tell, your suggestion is totally unrelated to this thread except for the appearance of the acronym, 'ODBC'.

Yeah. I reread topic. You are right. So I deleted my message.

I agree that the issue related to access level. OP should try to run installer as Adminstrator: right click on installator and "Run as Administrator".

I guess I can see how some confusion might have arisen here. The OP did mention that he had installed SQLiteStudio, although that has little to do with getting an ODBC driver for SQLite installed or used. So, maybe, that means the OP desires another GUI-driven application to access his SQLite DB(s). If so, saying so would be an improvement.

Your extension is clearly an ODBC client, something which uses the ODBC API and conventions to reach and call into a connection-string-selected ODBC driver. But what the OP has clearly and specifically requested is a "suggestion to download and install odbc drivers to connect to SQLite tables", after mentioning one such driver in particular.

As presented, the OP's problem is that the driver he tried to install failed to install, as shown by a specific error message, which error the OP hopes to alleviate. Perhaps that problem has been solved. Until we see more from the OP, there is not much more to be done for that problem than I suggested earlier.

Although this is an old thread. I thouhgt I'd post a reply in case it helps anyone else. I'm also running Win 10 (x64) and sqlite3 On the http://www.ch-werner.de/sqliteodbc/ page, instead of using the sqliteodbc_w64.exe I downloaded and installed the 32bit sqliteodbc.exe which seemed to work fine on my machine allowing me to connect to an SQLite3 DB using MS Access.

ODBC loads in-process. That means that the bitedness of the ODBC crud must match the bitedness of the program that is using ODBC.

That is to say that if you are using 64-bit MS-ACCESS you need 64-bit ODBC, and if your MS-ACCESS is 32-bit, then you need 32-bit ODBC. The same applies for anything else that loads in-process. If you have processes (programs) of differing memory models that require ODBC, then you must have duplicate ODBC drivers installed -- one for each supported process memory model.

Mixing bitedness within a single process (called in-process thunking) was IBM patented technology and as such Microsoft was required to remove it from Windows NT when they "converted" OS/2 into Windows NT.

By the time the patents expired on this technology all the 64-bit bittybox Operating Systems had implemented independant per-process virtual machines that only ran a specific memory model, and used a trampoline to access the Operating System.

As a result, only a few "big metal" Operating Systems from IBM support in-process thunking -- everything else applies the same model to all parts of a process, requiring the duplication of in-process bits where multiple models are supported.