🚀 go-pugleaf

The desktop version of our application currently uses BDE/ODBC/Jet with
Access databases. It is designed for a small workgroup with only one
updater.  Our next step is to use SQL Server and support up to 30
concurrent users. Only a few at most will be making changes. The others
will just be doing queries. 

The BDE is convenient, but we would like to dump that dependency. It has
already created installation and support problems for us, and it seems
to be at a dead end development-wise. My impression is that the main
trend in Windows is to ADO for data access. Is that right? What are the
tradeoffs or main points of using ADO vs. BDE/ODBC? Is either one even
suitable for a 30-user system? If not, what would be better? Our main
requirements are:

- 30 concurrent users with reasonable performance and high reliability
- vendor independence (no extra licenses or highly proprietary
solutions)

Network operation is not a consideration. We have our own multi-tier
solution for that. We just need to select a suitable server-side
database technology.

Thanks for any ideas.

Jim