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] "Mary Chipman [MSFT]" wrote:
> 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"
> <AxelHecker@discussions.microsoft.com> wrote:
>
> >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
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] <ToddC@discussions.microsoft.com> wrote:
>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
>
>"Mary Chipman [MSFT]" wrote:
>
>> 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"
>> <AxelHecker@discussions.microsoft.com> wrote:
>>
>> >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
Don't see what you're looking for? Try a search.