Question : .mdb vs .adp front end with SQL server backend

I have a question for an Access/SQL expert. I have created a MS Access application that has a frontend.mdb and backend.mdb using linked tables without a SQL server. Now I am wanting to convert to a SQL server backend. My IT department is telling me to have a frontend.mdb or .mde and they will build tables on the SQL server but the books I am reading say create a .adp frontend with a SQL backend but the books don't say why. What are the differences in .mdb and SQL vs. .adp and SQL. Is there any performance or security benefit with using .adp and SQL. Your opinion is appreciated. Thanks

Answer : .mdb vs .adp front end with SQL server backend

ADP was designed as a frontend for SQL Server, MSDE.
You typically set the connections to tbe backend when u create the ADP
ADP allows u to bypass JET AND ODBC (queries are executed on the server, so less resources required by cleint). ADP use Ole-DB.
But downside is you cannot create local tables
Now ADP's are usually smaller and perhaps a little faster

MDB's well u know how well they work and what u can do. If u use MDB, u will need to seutp a ODBC link and define linked tables
Big advantage is u can create local tables
Disadvantage is there are two extra layers of s/w between Access and SQL. This is the ODBC connection and Jet. So speed can become an issue.