How do you convert an mdb file to ADP?

qwertyjjj

Registered User.
Local time
Today, 02:56
Joined
Aug 8, 2006
Messages
262
How do you convert an mdb file to ADP?
 
I don't know the answer to your question but I believe you will find that an MDB can handle an SQL Server backed just fine.
 
it can but the efficiency is not very good.
with an adp, everything is passed to the back end to process rather than the client
 
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.
 
Since the .adp is being depreciated
Sorry Pat, just gotta correct you on this one:

deprecated

not depreciated, which is an accounting term for a way of writing off wear and tear on an object. :)
 
Sorry Pat, just gotta correct you on this one:

deprecated

not depreciated, which is an accounting term for a way of writing off wear and tear on an object. :)
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.
 
Oh, and if you look up DEPRECATED on Microsoft's website, you will see that they use THAT term, not depreciated. :D

If you put the term DEPRECIATED in on the MS website, you will get only accounting terms.
 
Well Bob, I stand corrected. I've not been using the correct term for a while now but I will mend my errant ways. :D
 
Yes, internally we use the term Deprecated.

--------------------
Jeff Conrad - Access Junkie - MVP Alumni
SDET - XAS Services - Microsoft Corporation

Co-author - Microsoft Office Access 2007 Inside Out
Presenter - Microsoft Access 2007 Essentials
http://www.accessmvp.com/JConrad/accessjunkie.html
Access 2007 Info: http://www.AccessJunkie.com

----------
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.
 

Users who are viewing this thread

Back
Top Bottom