Re: Official Status of SQLServer 2005 ADP

The Access MDB with linked tables is a superior tool to access SQL Server,
Oracle, DB2, etc. backends. The ADP was extremely limited in its
functionality which is why it never gained wide acceptance. It could only
link to SQL Server tables. It couldn't even link to Access/Jet tables!!!
It also required significantly different techniques to develop applications
such that about the only things an MDB and an ADP have in common is they are
both Access and they both use VBA.

My understanding at the moment is that future development of the ADP will be
limited or non-existent. In fact, with Office 12 which will be released
some time near the end of 2006, the ADP will not be enhanced to allow it to
create tables in SQL Server 2005. It will be able to access tables from
2005 but not create them. So, if you need to use the ADP to create
databases and manage them, you have to stick with SQL Server 2000.

Microsoft plans to continue support for existing ADP but will no longer
support creating them. I don't know what will happen with the upsizing
wizard. I hope it stays so it can be used to create the SQL Server
database. Otherwise, you would need to create the database from scratch or
use a tool such as erWin to translate the Access/Jet schema to SQL Server,
Oracle, DB2, etc.

"Terry M" <terrym@xxxxxxxxxxxxxxxxxx> wrote in message
news:%23mFW4XO$FHA.2520@xxxxxxxxxxxxxxxxxxxxxxx
>I just started reading this group and disapointed to read that it sounds
>like ADPs are being hung out to dry.
>
>
> I was not impressed by this. ADPs would allow someone with a bunch of
> Access programming background (like me) to leverage that knowledge to work
> with a SQL Server backend, without learning a new environment. If you
> program in Access you relize there is no faster way to built an
> application.
>
>
> If it is true that going forward less and less functionality, it could be
> hard to justify new development with ADP
>
> Those that have implemented (or plan to) these solutions may have an
> interesting support problem going forward.
>
> However everything I have read is not 'Official' does anyone know the
> status of this, or can you point me in the right direction.
>
> Thanks
>
>
>
> Terry Mc
>
>


.

Relevant Pages

  • 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: 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: Upsizing design considerations
    ... reports, with a ADP, or mdb (actually, it should be mde, or a ADE when you ... you would LINK the tables to sql server, and NOT USE a adp (the reasons is ... the first two remote users ...
    (microsoft.public.access.gettingstarted)
  • 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: 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)