Sqlite odbc12/21/2023 ![]() Subject: Power BI reading SQLite 3 vis ODBC strange behaviourĬheck your DSN to make absolutely sure you are pointing to the intended database file. In all cases, I have used a blank Power BI file with no model – I just load the transactions table and look at the latest date by sorting the date column in the data view. Power BI on the original machine still sees 11 th December as the latest transaction date and on a copy of the same database on another machine, 13 th Jan is the latest transaction date. You could use Excel, MS Access or even sql express. Another option could be to export the data to a. (your PC) Extract the data and convert it into a suitable format to import. ![]() ![]() I have tried deleting the database and the DSN and recreating from scratch and still get the same problem. One alternative could be install software on a 3rd machine. HOWEVER if I copy the database onto another machine and open it in Power BI then I do see the more recent transactions up to 13 th Jan (so they are there in the database). When I connect to the DSN with Power BI now and refresh the data I still see the latest transaction is 11 th December. The driver is usable but may contain bugs. The program has been running since and populating the database with new transactions dated as recently as today (13 th Jan 2020). This is an open source ODBC driver for the wonderful SQLite 2.8. I first created the DSN on 11 th December and read the data into Power BI no problem. I have program that creates a SQLite 3 datasource with a DSN that I then read into Power BI via an ODBC connection.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |