Re: Alternatives to ADP?

On Oct 20, 6:25 pm, el zorro <elzo...@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
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?

watch out for nested queries (queries that call other queries).
these will definitely cause round trips and bog things down if the
nest goes too deep.


.

Relevant Pages

  • Re: Question on conversion to ADP
    ... the money toward developping .NET technologies instead of Access. ... result of passthrough queries read/write instead of read only and also make ... database become corrupted when the users will start making their very own ... of ADP but what they are pushed toward is - how could I say that politely - ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Migration Questiion to SQL
    ... You can use the upsizing wizard but make sure you choose the link tables ... You do NOT want to create an .adp. ... will give you some ideas on what you might need to change in your queries. ... RecordSources. ...
    (microsoft.public.access.externaldata)
  • Re: Access Front-End with Sql Backend Tables
    ... If you use the upsizing wizard, choose the option to link the tables to the ... Don't convert to an .adp. ... >I have an Access database that I need to move the tables to SQL. ... > use SQL server as the database on the backend? ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Official Status of SQLServer 2005 ADP
    ... Plus many sub-tables with there own multiple table queries. ... some data from a second SQL Server database. ... I liked the idea of being able to do everything from the ADP (create tables, ...
    (microsoft.public.access.adp.sqlserver)
  • Queries missing in ADP and SQL after upsizing
    ... I am a rookie where SQL is concerned and I'm trying to create an SQL backend ... So I used the upsizing wizard to convert my ... database to an adp and link up all the tables in SQL. ... my queries are not showing up in SQL or the ADP. ...
    (microsoft.public.access.adp.sqlserver)
Loading