adp vs mdb

[Timtropolis]

Greetings all,

I did some searching on this but did not see anything that answered my question. My supervisor is requesting (demanding actually) that I switch
our Access app from an mdb file to an adp file. The app is standard fare(FE and BE, the latter residing on a server on our network). There is minimal login security (no mdw, just a lookup table with login nics).

My question for the experts is what is gained from doing this? In looking at the Access documentation as well as some of the other online boards, I really don't see anything that would warrant going from one to another.

Can anyone provide some examples as to why adp is a better solution?

Much thanks
Tim

 

[RV]

Tim,

if you google on ADP versus MDB, quite a lot of inetersting sites come up.
For instance this one:

http://www.pcreview.co.uk/forums/thread-2183599.php

HTH,

RV

 

[Pat Hartman]

The .adp is not being developed further. It will be supported in A2007 which is due out in the first quarter but you will not be able to design SQL Server 2005 databases. You will be able to link to an SQL Server 2005 database, just not modify its structure.

My advice - stick with the .mdb. If you want to upsize your data, that's fine. The .mdb will work fine with linked ODBC tables once you modify your forms so that their RecordSources are queries with selection criteria to limit the number of records returned. Read the KB articles on client/server optimization to see if you need to change any of your queries. Jet makes every effort to pass through EVERY query, not just specific pass-through queries.