I expect it should be possible, but I suspect it is overkill for what you are describing.
Adding QGIS to your workflow is beneficial when you either need to create quality visual maps, or when QGIS/PyQGIS is a useful coordinator for a more complex geospatial workflow.
It's not 100% clear from your question, but it sounds as if your core, i.e. master, platform is Access. So I would stay there and not bring QGIS into the picture.
You could access SpatiaLite extensions in SQLite, for instance ST_Buffer()
, to do the buffering and selection, and communicate with that from Access via the SQLite ODBC driver (see Loading Spatialite extension via SQLite3 ODBC Driver? for an old question on that here, may be easier now, not something I've tried).
If (as your question implies) you are only interested in [data]points that lie in a buffer around a specific geographic point, using any spatial platform may be overkill. Whatever your CRS is, distance is going to be approximately of the form SQRT(a*(x1-x2)^2+b*(y1-y2)^2)
, with a
and b
determined by the CRS and your location. So you could probably do your point selection within Access without having to involve multiple platforms.
If the rest of your workflow is in QGIS, and you merely want to run final reports in Access, I would still try to avoid potentially fragile ODBC connections, and instead do your selection, buffering, intersection in QGIS (including processing algorithms and PyQGIS etc). Then export a table with whatever your Access report needs as a csv, and then import that into Access as part of the reporting run.