Add sample starter code for a pure and safe read-only database reader application.

[MsftBrettShirley]

I have seen previous ESE database reader applications do some scary things in terms of their settings and behavior in ways that could be very disruptive or even create inconsistent DBs that the native application for that DB may not be able to recover from.

This work item respresents creating some boilerplate JET API start code, that would attach a clean database read only, and with no logging, and thus have no affect on the persisted ESE files. Such that the DB is not left inconsistent if the application should crash, nor have the possibility of creating a logical inconsistency for the native application that uses this DB.

Up-vote this issue if it is of interest.

[markfling]

A set of sample "best JET settings" prior to and after JetInit would be a great starting point, explaining the safest, and/or fastest parameter settings for a variety of scenarios. I spent more than a few days fathoming the JET_paramDatabasePageSize consistency requirement and coding a solution. There wasn't much out there on the web.