>All,
>
>We have a flagship app using C/S backend that now needs stand-alone capability- so that an auditor or other user can be sent an "extract" file on usb stick/download/email to be opened and processed on their machine without access to the customer's firewalled environment or anything else.
>
>The app uses Remote Views and SQL Passthrough so the goal is to re-use the C/S model, ideally with just a different dbc. For the standalone version there's no SP, SQL is quite standard and only one user at a time.
>
>The immediately obvious response is to use local views against dbfs for this purpose but that creates several risks, e.g. expensive support if one or more dbf/fpt/cdx files is inaccessible/missing on the user's PC for whatever reason but more importantly, dbf content has no protection. The app's subject matter is covered by privacy legislation in every market we look at, so dbfs are not viable if they're copied to external machines. Not keen to re-invent wheels or manage encryption ourselves, so we're hoping for a commercial option for what ought to be a fairly common need.
>
>SSCE and SQLite both seem to allow single-file databases with security and ODBC drivers, meaning existing C/S model can be used.
>
>SSCE seems to involve formal installation that experience suggests will be a support burden on random Windows machines of middle-aged auditors professing lack of computer expertise. However, SQLite seems to wrap all processing in the available 3rd party ODBC driver that accesses the database file directly- meaning if you can install ODBC, it should work.
>
>Does anybody have any advice or experience or better options of a lightweight database with ODBC driver, single database file and security? At this stage I'm thinking SQLite based on trawls of mostly several-year-old threads.

As an alternative to SQLite you can use MariaDB.
You need the bin and data folder and start the database using a command like the following:
start "MySQL DB" /min bin\mysqld --console --max_allowed_packet=128M --port=63306