On 2 Aug 2018, at 7:44pm, John R. Sowden <jsow...@americansentry.net> wrote:
> another point that I did not make clear. The accounting programs are not > associated with the technical programs, different people, different security > access. The tech databases and programs are in portable computers that go > out in the field, but not the accounting, etc. There indexes would have to > be updated when the computers are back at the office. That's not how SQLite works. It might help if you forget how FoxPro works and start again. In SQlite, a database file can hold one or more tables. If the database file holds a table, all the indexes of that table are stored in the same file. When the table is updated, all its indexes are updated immediately, as part of the same operation. It's not something that you have to worry about. It happens automatically. If you copy a databbase file from one computer to another, since the indexes are in the same file as the table, the indexes go with it. If you write an application that uses a number of tables, it's normal to put all those tables in the same database file. Copy one file, you have your entire database. Back that one file up, you've backed up your entire database. However, you can have one application access multiple database files at once if you need to. But if you have two tables in different files you cannot use SQL abilities like FOREIGN KEYs to ensure referential integrity. So most people don't do that. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
