In short, I have my data stored in SQL and load it into Excel which is used as a front end for final analysis. Basically, a lot of stuff is computed in C#, stored in SQL and then loaded into Excel.
I'm having minor issues - particularly since I'm updating intraday (either automatically or by discretion) - but so far I'm living with it. Issues being speed/stability when loading data.
Is Access both a database and a front-end?
Yes. And there are several options for doing this. As you know, Access can hold 6 object types: tables, queries, forms, reports, macros and modules in either a .MDB (older) file or an .ACCDB (newer). You can choose to put all objects into a single database. An alternative method is to put the queries, forms, reports, macros and modules into one "frontend" database, then put the tables into another "backend" database, then link the tables in the backend database to the frontend database. This allows the Access developer to work on improvements to a new frontend database while a different person continues to add/edit data in the backend database. If you consider it, the frontend is where the "smarts" reside and the backend is just the "dumb" data. In corporate environments, sometimes Access is used as a frontend database and Microsoft SQL Server is the backend database.
