Groups | Blog | Home
all groups > sql server clients > february 2006 >

sql server clients : MS Access as frontend to SQLServer 2005?


AxelHecker
2/15/2006 2:10:30 AM
It seems that I cannot create an MS Access project (ADP) to SQLServer 2005 as
I could with SQLServer 2000?

My MS Access has version 2002, SP3.

Any solution for this problem available? Thanks for any hint.

Axel Hecker
Kent Tegels
2/15/2006 2:14:07 PM
Hello AxelHecker,

[quoted text, click to view]

This is by design. Basically, ADP was really desgined for SQL7/2000. Given
some the changes like the XML Data Type, UDTs and the new LOBs, Microsoft
would have to update a significant amount of code in Access 10 and 11 to
support ADPs for 2005. I suspect there's just not the resources to do that
going forward since the focus is clearly on Office 12.

Thank you,
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/

Mary Chipman [MSFT]
2/20/2006 8:52:06 PM
To add to Kent's reply -- you can connect a completed ADP to SQLS
2005. To create the SQL Server objects, use the Developer edition of
SQL Server ($49). The license agreement restricts it to design-time
usage only, you cannot use the Developer edition with a deployed
application.

--Mary

On Wed, 15 Feb 2006 02:10:30 -0800, "AxelHecker"
[quoted text, click to view]
Todd C
2/21/2006 9:57:30 AM
I'm a bit confused by all the talk I have heard about ADP interaction with
SQL Server 2005. I have seen the limitation of creating server objects
directly from the ADP, but are there data issues as well? I know that the
advanced features of SQL 2005 won't be supported in ADPs for a while, but
what about the stuff that was already available in SQL 2000?

The reason I am asking is because I have re-designed and now support an
ADP/SQL application that I inherited from a business user. It needed better
security than the MDB level could allow, so we upgraded it to SQL 2000 with
an ADP front end. At the same time, we are looking to upgrade our servers to
SQL 2005. I have seen quite a few posts in this and other forums that talk
about Microsoft NOT recommending ADPs in the future. Are there ramifications
if all I want to do is use basic features already available in SQL2000?(I am
using SQL 2005 Developer and our Servers are, for now, SQL 2000 Enterprise)

Any comments, links, suggestions, etc. would be greatly appreciated.
Thanks.
Todd C

[quoted text, click to view]
dbahooker NO[at]SPAM hotmail.com
2/23/2006 11:35:17 AM
http://blogs.msdn.com/access/default.aspx

ADP's and Access 12 Security:

The ADP architecture is conceptually unchanged between Access 2003 and
Access12, which means that the features continue to work in essentially
the same way they did. We continue to believe that SQL Server makes a
great store for Access data and that building the UI either through
linked tables or ADPs will continue to work well.


ADP is the only route; MDB is for wimps.
Mary Chipman [MSFT]
2/26/2006 5:35:40 PM
Hi Todd,

If you want to run the application in 2000 compatibility mode in SQLS
2005, it's very easy to do that. Run sp_dbcmptlevel and set the
compatibility to 8.0 (See SQL BOL for more info). You won't get any of
the new functionality, but then again you don't have to worry about
the ADP breaking before you figure out what the best long-term
solution is.

--Mary

On Tue, 21 Feb 2006 09:57:30 -0800, Todd C
[quoted text, click to view]
AddThis Social Bookmark Button