Link to home
Start Free TrialLog in
Avatar of nickmark
nickmark

asked on

Sql Server Back End with an Access Front end (Size issue)

I am designing an application that has millions of records daily. If I were to make my back end a SQL Server database, could I use ACCESS as my front end, or would I have the same size issues (2Gig) that I would have in a native ACCESS application.
It is not going to be a particularly robust application. It is just reporting but there are going to be literally millions of records each 24 hours.
Avatar of Surendra Nath
Surendra Nath
Flag of India image

you can still use access as a front without any of the afore mentioned limitations...

The below articles might help you in getting started

http://www.techrepublic.com/article/using-access-to-build-a-front-end-for-sql-server/5065669
Yes, you can use Access, as mentioned above.

The key, with that many records, is to use the power of SQL server to do your analysis (use pass through query and stored procedures).

Only use Access to define how to write the SQL (define what fields you want or what values you want in the where clauses), or to present the results of queries or stored procedures that are run on the server.  

I've got an old book "Access Developers guide to SQL Server" (or something like that) which provides lots of good examples, but I think it was written for SQL Server 2000, but the concepts are still valid.  Don't know if there is an equivalent book on the market for Access (2007/20/13) or SQL Server (2008/12).

The key is to pass as little data across the network between your PC and the server as possible.
ASKER CERTIFIED SOLUTION
Avatar of Armen Stein - Microsoft Access MVP since 2006
Armen Stein - Microsoft Access MVP since 2006
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of nickmark
nickmark

ASKER

Great job
Thank you