ADP or MDB

J

Jacky Guttman

Hello,



I know ADP is an Access Data project and has to do with using SQL server. I
know MDB files are regular Application and it can be linked to a SQL server.



Is there a difference between the adp and mdb in the speed of the
applications?



My application is now running on 16 desks and linked to a .MDB Database, I
wont to link it to a SQL server DB because the speed, my problem is that I
have more then 25 complicated Queries, and I can not import it to a ADP
project, I have to write it again, so my question is: I it really advised to
use ADP project and to work some days to edit all the queries, or I simply
use a MDB application and link it to the SQL server, but I don’t wont to
loose speed!



Thank's for helping me,



Jacky
 
N

Norman Yuan

Van T. Dinh said:
See an earlier thread:

http://groups.google.com.au/group/microsoft.public.access/browse_frm/thread/e0f5f2a1f22f5621

The respondent, Norman Yuan, is a Microsoft Access employee (Engineer?).
Click to expand...

No, I am not. I am just an Access ADP user since its very begining
(Access2000+SQL Server7), and keep using it as SQL Server developing tool
(not as real ADP application), instead of Enterprise Manager. So, I try to
get me updated on the latest ADP information/rumors. The information in the
mentioned post ("MS Access team recommends using MDB as FE...") was read
quite some time ago on the MS Access team's blog.
 
V

Van T. Dinh

Sorry, Norman.

I must've mixed up your name with a Norman ? who used to frequent these
newsgroups and signed off his posts as Microsoft Support Engineer, I think.

The info you posted is correct, as per the Final Vision doc whose link I
posted.
 
D

David W. Fenton

My application is now running on 16 desks and linked to a .MDB
Database, I wont to link it to a SQL server DB because the speed,
my problem is that I have more then 25 complicated Queries, and I
can not import it to a ADP project, I have to write it again, so
my question is: I it really advised to use ADP project and to work
some days to edit all the queries, or I simply use a MDB
application and link it to the SQL server, but I don't wont to
loose speed!
Click to expand...

Keep it as an MDB. Microsoft is now deprecating ADPs, which have
never been made to work reliably (things that are broken in one
version get fixed in another, but in that next version things that
were previously OK are now broken). Many people who tried to use
ADPs have abandoned them to go back to MDBs. But my observation is
that there are still a large number of developers out there still
wanting to use ADPs. My guess is that those were people who'd never
had anything but trivial involvement with MDBs in a client/server
environment.

The answer to your question is very easy:

You already have an MDB. Keep it. Revise what doesn't work well over
ODBC so that it works better.

Starting over with an ADP would be foolish, especially since it's
pretty clear that ADPs are not the future of Access any longer.

(how many things first released in A2K that were THE FUTURE OF
ACCESS have now been wholly abandoned or deprecated? Almost all of
them!)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Easy way to copy data from from data source to another? 3
mdb to adp subform problem 2
Switchboard Manager disable 0
Alternative to GoToRecord acNewRec for Access ADP 3
mdb to adp 3
Clearing ASP.NET caches via adp 3
How to convert mdb -> adp ? 6
schema to text file 7

Top