var sidebar_align = 'right';
var content_container_margin = parseInt('290px');
var sidebar_width = parseInt('270px');
Unanswered: .mdb Front -----> SQL Back End
I would like to do the following:
1) Create an .MDB (not .ADP) front end using Access 2k.
2) Use SQL 2k as the back end.
3) Data access using ADO.
4) Not use linked tables.
5) Use either SQL tables or Stored Procedures.
I'm ok running Stored Procedures or opening recordsets to read, add or delete records. No problem.
What I would like to do is create Access Reports that use either SQL tables or the output from Stored Procedures as the Record Source.
Remember. No linked tables.
Is this possible? Can somebody explain how to do this?
I use Stored Procedures to gather the data for my reports and then use a pass thru query in Access. I use that pass thru query in Access as the datasource for the report.
I have a much more stable system when I let SQL Server handle everything and then just pass it to Access.
I run a ship very similar to one which you are describing.
I would heartily recommend looking into using an adp as opposed to an mdb. For starters, as I'm sure you've noticed T-SQL is much easier to work with then JET. Also, you may still use all of the features available in MSSQL Server (security schema, UDF's, triggers etc).
The report design itself is the same. Which is why we still use access.
I agree with you except I'm having a problem (in my head) giving up the option of creating temporary tables in my Access application.
You're not giving up temp tables silly!
You can create temporary tables server-side by prefixing your table name with a '#'
Depending on what you need the temp tables for, you may even have server side options that will get you around the issue entirely.