Re: Alternatives to ADP?



Another thing to look at, which Sylvain touched on, but didn't quite highlight is to write your queries on the SQL Server side, and
then attach them in Access as either Tables or Pass-through Queries. This should result in speeds comparable to ADP, though you
have the disadvantage that you have to worry about linking them in...not so much a problem if your server is reliably in one place,
but definitely an issue if you ever change servers or you have some kind of server fail-over topology going on. (If that last
sentence was Greek to you, you almost certainly aren't in either of those situations, so don't worry about it <g>.)


Rob

"el zorro" <elzorro@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:154C6D3B-2225-4F22-BC2D-1BFC99597C0E@xxxxxxxxxxxxxxxx
I am currently experimenting with upsizing a front end/back end Access 2000
database (via the upsizing Wizard) and have found that keeping the front end
an mdb with the back end converted to SQL Server 2000 results in
excruciatingly SLOW execution speeds for the queries. As I understand it,
this is because the queries (about 50 of them) are being executed on each
workstation, not the server. Some of these queries are pretty complex, but
they are essential for most, if not all, of the reports and forms to function
correctly.

So I am now testing the other upsizing option that creates an adp file. Only
about half of the queries made the migration successfully, but preliminary
testing of the partsthat do work indicates that the adp approach will result
in much faster
response times for the user.

HOWEVER, I am concerned about the posts that suggest Microsoft is
dropping support for adp. One of the reasons I have been asked by the Powers
That Be to upgrade the database is to allow for future growth. I'm not sure I
can claim that adp is the future.

Are there any long term alternatives to adp that will allow me to migrate to
a more robust platform (with the queries on the server) without having to
completly reprogram my current Access database?
Thanks!



.



Relevant Pages

  • Re: From .mdb to .adp database
    ... there is no exact equivalent query object in SQL Server to MDB's query. ... Most likely, the wizard converts MDB queries to Viwes or SP, if the queries are convertiable. ... Also, when you decide to use MDB front-end, you can choose use MDB queries in the front end or use SQL Server side query objects. ... SQL Server is very powerful server software, whether you use MDB, ADP or anything else to access data from it, you MUST learn how to use it and almost for sure you need to learn another programming environment. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: From .mdb to .adp database
    ... there is no exact equivalent query object in SQL Server to MDB's query. ... Most likely, the wizard converts MDB queries to Viwes or SP, if the queries are convertiable. ... Also, when you decide to use MDB front-end, you can choose use MDB queries in the front end or use SQL Server side query objects. ... SQL Server is very powerful server software, whether you use MDB, ADP or anything else to access data from it, you MUST learn how to use it and almost for sure you need to learn another programming environment. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: From .mdb to .adp database
    ... I decided to go on with adp project, and i have created a store ... But queries are different stories. ... In SQL Server, there are Views, Stored Procedures, UDFs. ... Also, when you decide to use MDB front-end, you can choose use MDB ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Official Status of SQLServer 2005 ADP
    ... solution might be to use ADP. ... With MDB and Linked tables, the only ways of accelerating things are the use ... of Views and the cumbersome use of SQL passthrough queries. ... > SQL Server, and carry on using Access like I aways had. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Alternatives to ADP?
    ... With MDB and ODBC linked tables, simple queries should be done on the ... server, not locally. ... For ADP, don't expect any new features in the future but I will be surprised ... That Be to upgrade the database is to allow for future growth. ...
    (microsoft.public.access.adp.sqlserver)