- Joined
- Sep 6, 2011
- Messages
- 6,211
- Location
- Philadelphia
- Tractor
- John Deere 3033R, 855 MFWD, 757 ZTrak; IH Cub Cadet 123
Yep. Understood. But other than the "slow" part, the rest all sounds like it's geared just for me.MS Access front end / User Interface, SQL backend. MS Office products are bloated, slow, and get quirky when asked to do too much.
There are always users that can't be trusted so the Access user interface protects the backend data while SQL does the heavy lifting.
Oh, and I'm running this mostly on huge multi-socketed PC's, none fewer than 32 physical cores, with NVMe drive arrays. Point being, "slow" may not affect me as much as the average user, assuming Access (like recent Excel) can actually make use of multithreading.