Okay. Do you really need all of the terminals to have up-to-date data from all the terminals ?
If not, it's a simple problem: each terminal sends data to the master, which puts all the incoming data into the same database. Terminals don't need a SQL dataase at all. They simply report changes to the master, as often as they need to. Information send from each terminal can be in the form of a text file of new data in CSV format. Incoming text files pile up in a directory on the master. It is important that the master does not try to process data into the SQLite database immediately, since this would introduce a delay and perhaps problems with locking. It's faster just to accept the data and store it in a file on disk, and worry about processing it separately. A program on the master server continually reads any file available, adds its data to the central database, then deletes the file. If there are no files waiting to be processed it can idle for a second or two. Another program, which can run at the same time, gives you access to this database so you can read the data and do your maintenance. Does that work for you ? _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
