ODBC vs OLE DB

Hi All, does anybody know the pros and cons of using ODBC to connect an Access front end to an SQL backend, vs using Access projects.
ThanksAre you thinking of migrating an existing application or starting a new project. In case of migration, ODBC gets things running much faster and you have all that nifty access-features you are used to work with. Porting to adp ends up with a lot of rewriting. On the other hand, you have immediate access to stored procedures, views, triggers, transactions etc. that are more then useful.
ADP is, uhm, not-so-well documented imo. You are forced to use ADO which is somehow inconvinient in the beginning but more robust in my experience.
So if you are migrating, it mainly depends on your need to use SQL-Server features.
If you are starting a new project and have the time (and nerve) to play around with something new, I'd recommend to go for adp.|||My case is the second one. I am thinking of starting a new Project.
The only think that made me think twice about it is that when I connect to my SQL backend, its faster than my adp file that is connected to the same SQL database from the same machine. Maybe thats because I don't have a lot of data at this point.

Thanks

Originally posted by chrisp_999
Are you thinking of migrating an existing application or starting a new project. In case of migration, ODBC gets things running much faster and you have all that nifty access-features you are used to work with. Porting to adp ends up with a lot of rewriting. On the other hand, you have immediate access to stored procedures, views, triggers, transactions etc. that are more then useful.
ADP is, uhm, not-so-well documented imo. You are forced to use ADO which is somehow inconvinient in the beginning but more robust in my experience.
So if you are migrating, it mainly depends on your need to use SQL-Server features.
If you are starting a new project and have the time (and nerve) to play around with something new, I'd recommend to go for adp.|||ODBC connections seem to be faster locally. My expieriences for network connections are exactly the opposite.

You should use Acess 2002 (adp is new for 2000 and not that stable;) and you should make yourself familiar with Enterprise Manager and Queray analyzer (if you aren't already). Then you have data and presentation separated, a fairly good ide and admin environment and all MSSQL features at hand.

We migrated a large project late 2001 and are since working with adp and I'm quite happy with it.