Re: Official Status of SQLServer 2005 ADP

I guess what we have been looking for is a way to use Access as a front end
for SQL Server.

We have an old Access multiuser app with an MDB backend that has a hundred
or so tables, that is nearing the end of its life.
Performance is a big issue for us. This app is for analyitical lab results
and has reports based on some very complicated queries bases on a dozen or
more tables. Plus many sub-tables with there own multiple table queries.

I though that using ADP would allow me to use SQL views, SP's, etc to speed
this up considerably by puting the query processing load onto our SQL
Server, and carry on using Access like I aways had. Plus I need to draw
some data from a second SQL Server database.

If you think that linked SQL Server tables with a Access front end could
work as well or better I would feel better. Does this mean I would use ODBC
and write passthrough Queries?

If you can point me in the right direction I would appreciate it. With the
exception of an A95 app I wrote years ago (that did some ODBC passthrough
queries to an IBM AS400 database) I have been working with the standard
split FE/BE mdb model.

I liked the idea of being able to do everything from the ADP (create tables,
view, SP) but that would not be the end of the world.

At the end of the day I would like to create a frontend with the ease of
Access and let SQL Server do the heavy lifting.

Thanks




"Pat Hartman(MVP)" <patsky@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23681X3P$FHA.1568@xxxxxxxxxxxxxxxxxxxxxxx
> 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 s
> 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: Access 2003 to SQL Server 2000 over a VPN
    ... Coming back to the original VPN discussion... ... Would you consider using an ADP talking across an fast broadbank link to ... local database, but ideally we would like to centralise. ... Would SQL Server replication be an option, ...
    (microsoft.public.access.adp.sqlserver)
  • ADP, Application Role, and objects
    ... The above link is to an atricle on how to implement SQL Server Application ... After you connect with your ADP, fire a bit of code to set the ... third party tools to view the data on the same database. ... Scenario 1 - If I explicitly grant permissions on that object to the user ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Access 2003 to SQL Server 2000 over a VPN
    ... you're careful about your database design, though, that may be the way to ... As a result of the difficulties I've had, I try to avoid SQL Server ... Would you consider using an ADP talking across an fast broadbank link to ... A thin client interface has been suggested, ...
    (microsoft.public.access.adp.sqlserver)
  • RE: SQL Server 2000 & Access 2007 Project
    ... You have indicated that the Access database is an Access Project file (ADP) ... occurs when we attempt to open the same table's design view in the Access ... so that SQL server cannot get the type of the data in the design view. ...
    (microsoft.public.sqlserver.clients)
  • Re: Looking for a professional SQL programmer for a small job
    ... Pro SQL Server 2000 Database Design - ... I have two queries to build and while I know my way around SQL, ... >> One is a seach query that pull rental properties from a database based on ...
    (microsoft.public.sqlserver.programming)