I see you've been fixing up things some more
Meanwhile added support for old MS Access Jet driver (as present in MDAC components etc)... saves a download for older systems (XP, ...) that probably have it preinstalled.
Some remarks/discussion points if I may - as the general program structure and coding is fine, I'm looking for other things to moan^H^H^H discuss
- The .lps file could be kept out of version control so that each developer can maintain his own editor environment, breakpoints, build mode etc.
- The inno setup files could use relative paths instead of absolute paths; makes it less system-dependent
- The function DeleteUser need not delete all records from the user if a foreign key reference with cascading delete was specified (at least possible in mysql, firebird, ms access, probably in sqlite, too but no exerience there)
Defining referential integrity will also avoid ever adding records for non-existing users, and enforces data integrity when other code/users access the database without using the application
- Export functionality (to Excel, Access, CSV,...) might be nice? There's ready made code to export a dataset in
https://bitbucket.org/reiniero/db2securityscript/src, directory OutputParser (dataset2sql.pas, databaseexporter.pas, CreateAccessDb.pas) which I'm happy to additionally license as LGPL.
- Noticed two Firebird .fdb in pristinedbs. The _empty one is not referenced in the Inno setup script - perhaps that could go? Or is there some other reason to keep it there?
Edit: oh yes, of course, as long as we're allowed to discuss feature creep: what about nice charts and graphs? Everybody loves those
(More or less kidding - I like the clean and concise minimalist approach in the current program)