SQLite is a library that is built into applications. Other than sqlite3.exe, its not a standalone 'thing', if you will. If your application can't be rebuilt to directly write to a SQLite database, then the only alternatives I can think of are - to keep doing what you're doing, or, - look at your monitoring application to see if it has some kind of API that can talk to an external application or service and write the application or service to handle the requests, or - If your application can pipe its findings to a text file, an application that watches for these text files changes could be written to deal with the output of your monitoring program.
On Fri, Jun 8, 2018 at 1:26 PM, <lhelger...@surplushunter.net> wrote: > > Hello - > > I've been following for a while, a lot of very intelligent > people here, and not a lot of fuss!!! Very nice, my compliments to > all!! > > I'm just learning SQLite and using it to collect alarm values from a > monitoring system. The monitoring system can't access the SQLite file > directly, so I've been using sqlite3.exe as the intermediate. > > Since I'm > making many access to the database the monitoring program is constantly > launching sqlite3.exe with new commands or files of commands, very wasteful > of resources. (Windows 7) > > Is there a platform/program that can be run as a > SQLite "front end" that could be launched once and take commands from > another program and pass back results, or is there a way to do that with > sqlite3.exe? I've looked around the web and not found anything, so > far. > > Any guidance is greatly appreciated, thanks for your time!! > > Leland > > _______________________________________________ > 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
