[AccessD] ADPs in the future

The problem has been know about for some time. SQL Server 2005 is a major 
rewrite and at the time they began development they decided they would not 
provide access to its features from Access and ADPs mainly becasue they view 
Access as a power user application - STILL. Lot of .NET stuff built into 
SQLS erver 2005 and they figured it wasnt worth the cost or effort to 
rewrite the ADP functionality in Access to deal with this.

The next version of Access is being previewed in the UK at a user group 
meeting on 11 Nov. According to the publicity they (MS)have rebuilt the 
Access dev team including a new prroduct manager and it is believed major 
changes are being worked on.

I remember replying to that email from Mary Chipman on an MS Newsgroup 
saying this was one of Microsofts more stupid ideas. I also recollect 
telling the Access project manager the same thing at least a year ago.

Martin




----- Original Message ----- 
From: "Dan Waters" <dwaters at usinternet.com>
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Sent: Wednesday, September 22, 2004 2:18 PM
Subject: RE: [AccessD] ADPs in the future


> Hello to All,
>
> Well, I am now confused.  I have read that Access 2003, as an ADP, 
> includes
> a builder for stored procedures.  Why would MS add this feature to a 
> product
> if it can't be used?
>
> There has to be more to this story.
>
> Dan Waters
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
> Sent: Wednesday, September 22, 2004 4:47 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] ADPs in the future
>
> Hi Marty
>
> Though I haven't played with the "Express" versions, this sounds
> interesting. I have, however, no idea why "CLR assemblies and complex
> data types" would require a complete rewrite, so could you please
> spell out for SQL 2005 dummies like me, what this message means?
>
> What I read is that an Access ADP cannot - and will not be able to -
> work with SQL 2005 ... I guess "SQLS 2000 compatibility mode" is not
> something you can turn on and off but something you choose at
> installation time.
>
> /gustav
>
>
>> Just in passing concerning future design
>> about ADP's from Access 2003 on down that will not play fair with SQL
>> Server 2005 Express (replacement for MSDE).
>
>>  Re: Access 2002 and SQL Express
>>  From:  "Mary Chipman [MSFT]" <mchip at online.microsoft.com> Sent:
>> 8/20/2004 11:30:58 AM
>
>> You will not be able to use any of the designers with SQLS 2005
>> databases, whether it's SQL Express or the Developer edition. IOW, you
>> won't be able to create databases, tables, views or any other database
>> objects from an ADP. The only support that is envisioned is that you
>> will be able to connect an Access front-end to a SQLS 2005 back end if
>> it is running in SQLS 2000 compatibility mode, so your forms, reports
>> and other local Access objects should still run. There is no service
>> pack or quick fix being planned as far as I know because of the amount
>> of work it would entail. If you stop to think about it, it's pretty
>> hard to see how accomodating new Yukon features like CLR assemblies
>> and complex data types in the ADP designers could be achieved without
>> a complete rewrite.
>
>> --Mary Chipman
>
>> -- 
>> Marty Connelly
>> Victoria, B.C.
>> Canada
>
> -- 
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> -- 
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>