The efficieny of the .mdb is fine. Since the .adp is being depreciated, I wouldn't recommend creating new .adp applications or going through the effort of converting an .mdb to an .adp.
Jet makes every effort to pass through all queries to the server. If you are having issues, you need to understand what you are doing that is preventing that from happening. Take a look at the KB article on optimizing for client/server. It should give you some things to examine.
Sorry Bob but I've got to side with Pat on this one. Depreciation is a way to decrease the value of an item which is what Microsoft is doing with ADP in Access.
Sorry Bob but I've got to side with Pat on this one. Depreciation is a way to decrease the value of an item which is what Microsoft is doing with ADP in Access.
Well, according to Dictionary.com (looks like deprecated fits BETTER):
Depreciated:
1. decrease in value due to wear and tear, decay, decline in price, etc.
2. such a decrease as allowed in computing the value of property for tax purposes.
3. a decrease in the purchasing or exchange value of money.
4. a lowering in estimation.
Deprecated:
adj. Said of a program or feature that is considered obsolescent and in the process of being phased out, usually in favor of a specified replacement. Deprecated features can, unfortunately, linger on for many years. This term appears with distressing frequency in standards documents when the committees writing the documents realize that large amounts of extant (and presumably happily working) code depend on the feature(s) that have passed out of favor.
----------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.mspx
----------
A slip of the mind/fingers. You are of course correct. In any event, if MS has deprecated a feature, it has no future and new development should not be undertaken.