I have been developing in Access for many years but I'm fairly new to doing so with a SQL server back end. My other backends have been Access mdb or accdb's.
I'm starting to work on reports in the project and wonder what kind of techniques Access developers use when the backend is SQL Server.
In prior projects using an Access back end I would sometimes set up a standard query combined with input parameters to create a temporary table in the Access front end and bind the report to the temp table. Other times I would bind the report directly to a query.
We are using SQL server because the data size of about 250GB is far beyond the 2GB access limit. Since the data is so voluminous the 'create a temporary access table to drive the report' approach is not feasible.
So far in my SQL learning curve I have bound a form to a recordset generated from a stored procedure. I can see this also being done to bind a report to a recordset returned from a stored procedure. The selection criterion would be passed as parameters to the stored procedure. The SP would then return the filtered (based on the past parameters) recordset which would bound to the report.
I just wanted to check with the EE experts before heading down the wrong path.