Re: MS Access as frontend to SQLServer 2005?

Tech-Archive recommends: Speed Up your PC by fixing your registry

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
<ToddC@xxxxxxxxxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxxxxxxx> 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

.

Relevant Pages

  • Re: ADP Vs. ODBC
    ... that Access connects to SQL Server and consumes server and network ... Actually, an ADP will often hang on to more than one connection, so there's certainly a point there, and I can understand that ODBC gives you greater flexibility, but am I wrong in thinking that it usually requires a significantly increased amount of maintenance and tuning compared to an ADP? ... you can't do back-end design work from an ODBC front-end either. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Future of ADPs
    ... linking tables with MDB and a SQL. ... (ADP and SQL) thing that could not be done by a MDB. ... SQL Server 2005 Express and ASP.Net, ... Reports to design your reports. ...
    (microsoft.public.access.adp.sqlserver)
  • A little OT - Quite a rant on microsoft.public.sqlserver.olap
    ... SQL authentication doesn't work for SQL Server to anywhere. ... reports in ADP; but somehow it's not getting traction. ... thru in order to create forms and reports against a database. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)