[dba-SQLServer] Upsize wizard and named queries

>do you have a link?... as for the inline editing of the SPs, that does not
affect me on my platform as I prefer QA than the ADP as sql dev tool.

http://www.databaseadvisors.com/gazette/sqlexpress.htm

 Thinking about Access and SQL Server 2005
Might I suggest: Plan to plan and test carefully too.
http://lab.msdn.microsoft.com/express/sql/
http://www.tegels.org/qara/

There's been an interesting thread on the SQL Server Newsgroups about this
topic. A developer was trying to create an ADP to work against express and
got this message:

You have connected to a version of SQL Server later than SQL Server 2000.
The version of Visual Studio or Access that you are using was released
before the version of SQL Server to which you are connected. For this
reason, you might encounter problems.

Mary Chipman from Microsoft posted this response:Andy Baron and Mary Chipman

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.

That said, with Access 2003, I was able to connect up to an instance of SQL
2005 (not in 2000 compatibility mode) and work with data with SQL2000
compatible data types. I was also able to stick XML into an XML-typed (but
not strongly-typed) column and have it work as expected.

The bottom line here seems to be that ADPs aren't worth investing new work
into today if you plan to go to SQL Server 2005 with them. However, my
limited testing of Access 2003 as the Frontend and SQL Server 2005 as
backend using linked tables seems to be okay. Time will tell, of course.

microsoft.private.sqlserver2005.dataaccess
http://communities.microsoft.com/newsgroups/default.asp

To amplify what Kent said, there are no plans for supporting designing SQL
Server objects using Access ADPs either now or in the future. You can use
Access to connect to a SQL Server 2005 database in 2000 compatibility mode,
but there is no support for new 2005 functionality being planned. It is
recommended that you use the client tools in SQL Server for creating new SQL
Server objects. There is also support in Whidbey for creating SQL Server
objects.

posted on Friday, August 20, 2004 2:03 PM  


John W. Colby
www.ColbyConsulting.com 


-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco
Tapia
Sent: Wednesday, January 25, 2006 7:39 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Upsize wizard and named queries

do you have a link?... as for the inline editing of the SPs, that does not
affect me on my platform as I prefer QA than the ADP as sql dev tool.



On 1/25/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>
> MS has plainly stated that ADPs will not be supported (at least in the 
> same
> way) in future versions of Access.  They don't break but the inbuilt 
> editing of SPs etc go away.
>
>
> John W. Colby
> www.ColbyConsulting.com