What are the differences in MDB and ADP?

Ashfaque

Search Beautiful Girls from your town for night
Local time
Tomorrow, 01:11
Joined
Sep 6, 2004
Messages
897
Hi Gentelmen,

As I am venturing from mdb files to ADP I would like to know the followings:

1. What is the major difference in MDB and ADP other than the back end of ADP are SQL Server.

2. Are the sizes of ADP always lesser than MDB?

3. Do the ADP have much more speed in opening forms, running queries and generating data rather than MDB?

Thanks in advance.

With kind regards,
Ashfaque
 
2. Are the sizes of ADP always lesser than MDB?

- not always. Nothing is ever "always"

3. Do the ADP have much more speed in opening forms, running queries and generating data rather than MDB?

- they should, unless the connection to your server is bad.
 
You can get most of the benefits of an ODBC data source and none of the problems associated with an .adp if you only upsize the tables and leave the rest of the application as an .mdb.

Make sure that ALL of your forms/reports are based on queries with selection criteria to limit the data returned from the server. If you don't do this, Access will be slower than it was originally. Upsizing to an .adp won't fix this. You would need to make the same changes in the .adp.
 
Thanks Pat and Crilen007,

After reading the various articles reffered by you gentlemen, I came to the conclusion that both ADP and MDB may have little compliations if I use them and FE and back end ovet to MSDE.

At present my FE & BE both are mdb files with linked tables in FE. The FE holds tricky codes and it has enough beauty as I had hard efforts which I do not wish to loose.

As Pat says;
You can get most of the benefits of an ODBC data source and none of the problems associated with an .adp if you only upsize the tables and leave the rest of the application as an .mdb...Upsizing to an .adp won't fix this. You would need to make the same changes in the .adp.
So if I do take care of my other objects which all (should be) based on queries, would make easier to keep FE as ADP.

MDB troubles when it concern with speed up matter where as ADP could carry out the action fast.

Its like I stand on center of the bridge....dont know which side is closer to me....

Finally, my first attemp would be try to keep my BE (tables only) on MSDE and FE as ADP ensuring that rest objects are based on queries and not directly dealing with tables. B4 doing this I off course will keep a back up of my mdb bcz I dont want to loose codes and beauti of my FE as I said and then would revert back to MDB incase I face any hard critical problem with ADP FE.
But I hope it would work.

Thanks for the advice.

With kind regards,
Ashfaque
 
Perhaps it will help you to decide if I tell you that I never use .adp's. I have tried them with each new version of Access and they are always lacking in functionality that is available to the .mdb. One thing I found particularly annoying was the inability to link to tables in Access .mdb's. How silly is that?

If you don't have SQL enterprise manager available to manage the MSDE database, you will need a single .adp to manage your tables should you need to make any changes once you upsize the db. The .adp is quite limited in its ability to manage a MSDE or SQL database. I have SQL Server installed on my PC so I always use Enterprise Manager and I have been spoiled by that really good tool.

My suggestion:
Upsize but leave the fe as an .mdb
Make sure that all forms/reports are based on queries with selection criteria (you would need to do this for an .adp also)
Create an .adp to use to make any physical table changes once you have upsized to the MSDE database.

MSDE by the way is simply a crippled version of SQL Server. Take a look at the SQL Express product which can be downloaded for free from the Microsoft website. It is the MSDE replacement for future versions of Access.
 

Users who are viewing this thread

Back
Top Bottom