Ridiculous to be sure; but a production environment using a split access database cannot be disrupted; so building scaffolding around the production access tables for reports, etc.
If proof of concept materializes, then SharePoint could well take over as it was intended; where sql on SP will be the back end, access front end can continue to do the job as it has in the past and SP can start doing the things it does to serve information based on common (access front end and sp) sql data.
Now question; is it possible to routinely export access data to a sql instance that sharepoint can use for external content? Keeps the access tables db alive and alone in production, whilst sharepoint dev/test can continue using somewhat live data. I see no way for sp to connect directly to access db tables, which would be best outcome. Have successfully exported access tables to sp using access and all looks fine. But given data is a one time load from access to sp; how to keep the sp data up to date, at least once/day?
As I said "ridiculous" to be sure, but best idea I've had to get out of the rut and allow sp dev lab to progress, while access live db stays untouched in production.