BillPowell
asked on
Long winded ADP ADO OLE DB ODBC question
Im wondering if someone can give me some explanation regarding these layers of communication. If find them quite confusing. In particular, the hype regarding how great Access ADP files are because of their native connectivity with SQL Server. In my limited experience with them, I have found them to be rather cumbersome and limiting. I appreciate the speed advantages they have over linking SQL tables to an MDB file, but theres some downsides as well. Not being able to use local tables is definitely one of them. If you have full access to SQL server, then you can create your views, sp's, triggers, tables etc, then using ADO you can open or call any of these objects directly from an MDB file. At the same time you can link to other data sources using ODBC. Is using ADO to call an sp or open a recordset from MS SQL the same as connecting with an ADP file and binding views to your forms.
Sorry if this question is kind of all over the place but Id like to get these things straight, to help me make decisions in designing future apps.
Regards,
Bill
Sorry if this question is kind of all over the place but Id like to get these things straight, to help me make decisions in designing future apps.
Regards,
Bill
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
In the first case you described the ADP still has the advantage.
In the second case obviously if you'd wish to upgrade to vb.net you'd be able to use the ADO code & not the mdb
In the second case obviously if you'd wish to upgrade to vb.net you'd be able to use the ADO code & not the mdb
ASKER
Thanks for the input guys. Ive been gathering more info and reading some other links too, and I think Im getting a handle on it.
Regards,
Bill
Regards,
Bill
also check out the Microsoft newsgroup: Microsoft.public.access.ad
ASKER
Thanks for the responses. I guess if your using MSDE and dont have access to full MS SQL with enterprise manager, this can be a big advantage of ADP's. I guess theres one thing still puzzling me about ADP's MDB communication to SQL server. Lets say you write an app with an MDB file. You dont link the sql tables, but instead access them through ADO code calling stored procedures and views etc. You can still use some local tables if needed, thus maintaining some flexibility. In this scenario, would the ADP still have any performance advantage over the mdb. Also, would either of these two scenarios be more favourable if you decide to ditch access and upgrade to vb.net as a development tool?