Pt 1 solved. Win 10 OS sees the sqlite3.dll if its in SysWOW64 but not if its co-located with the .exe...Thanks Bill Gates.
dbannon - Examples you cite do work after pt. 1 above. The app examples though seem to have major issues or the debugger is really confused. Stepping through the code, it doesn't like the attributes of TSQLScript. Example:
var
OurScript: TSQLScript;
begin
OurScript:=TSQLScript.Create(nil);
try
OurScript.Database:=FConn; //Indicate what db & ...
Inspecting OurScript.Database, the debugger says that TSQLScript does not contain a .Database attribute. Inspecting the class as presented by the debugger (by hovering), this is true.
Sqlite vs. SQLite3. The example uses 3:
LoginForm.ConnectorType.AddItem('SQLite3', nil);
This is the dll I've downloaded and as above, works with the other example.
I'd say that from the time this example was created, things have changed. This is at least true for the assumed target environment (i.e. the example is no longer "plug and play"). It would also seem to be the case that there's a disconnect between the source code and the current example set, at least as pertains to SQLite(3). There are likely also problems with Firebird although I didn't spend much time looking at FB. Probably its time to update the example(s).