Re: Why does SQL server 2005 not work with Access 2003 Projects (adps)?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



I aggree with you. Actually, I alway use Access ADP as my tool for my SQL
Server development. The copy/paste server objects with ADP is very handy.
However, if MS decided not making Access2003 support SQL Server2005 server
object manipulattion, what you can do? With ADP possibly going away soon, I
do not see MS would make extra efford to give Access2003 and older a push on
this regard.

"Jello World" <jello_world@xxxxxxxxxxx> wrote in message
news:1165260570.842541.188350@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Norman;

we don't 'insist on using adp'

adp just flat out works better.

can you copy and paste views in Enterprise Manager?
can you copy and paste views in SQL Server Management Studio?


-Charlie



Norman Yuan wrote:
What do you mean "does not work" here? If it means "SQL server 2005
databases cannot be accessed through Access 2003 projects", that is not
true, or at least, depending on the meaning of "be accessed", not
complete
true.

Yes, you can access SQL Server2005 database with Access2003 ADP, your ADP
app will run fine. You just cannot use ADP to create/modify SQL Server
2005
server side objects (table, view, sp, UDF...) as you used to be able to
with
Access2000/2002/2003 and SQL Server2000. This is understandable: SQL
Server
was released 3 years after Access2003's release and when Access2007 was
on
its way. Of course we could complain that why MS does not release an
Access2003 patch, as they did with Access2000 when SQL Server2000 was
released after Access2000, so that Access2003 can work wirh SQL
Server2005
the say way as with SQL Server2000.

Yes, if you insist to use Access ADP as tool to design/modify/manage SQL
Server2005, you need to move up to Access2007. If you only want to run
your
ADP app as front-end, Access2003 would be fine. I wouldn't bet my new
development on ADP, which may not be there any more in next Access
release
(purely guessing).

"J.S." <jss@xxxxxxxxxx> wrote in message
news:OQ480K6FHHA.320@xxxxxxxxxxxxxxxxxxxxxxx
I know there are other ways to connect to SQL server but I am wondering
why
SQL server 2005 databases cannot be accessed through Access 2003
projects.
Is it to force people who prefer the Access interface to upgrade to
Access
2007?



.



Relevant Pages

  • Re: Future of ADP - new article
    ... Start an Access2007 ADP, which connected to a SQL Serverdatabase. ... "Office Access 2007 offers two ways to connect to SQL Server data: ... to SQL Server is MDB file format or ACCDB file format. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Query Speed ... Access XP vs Access 2000
    ... With adp all SQL processing is done on the server. ...
    (microsoft.public.access.externaldata)
  • Re: .mdb, .adp and SQL Features and Benefits
    ... user's machine) that accesses one central MDB backend. ... So is an SQL BE for me, how would I do it, and what is an ADP? ... One should not move to Server back end for performance reasons. ...
    (comp.databases.ms-access)
  • Re: "I want MyMDB" (apologies to Mark Knopfler)
    ... The .adp does just what you are suggesting. ... .adp projects are MS Access front-ends that hook up to a MS SQL ... Server back-end. ... What I was suggesting is that the back-end should be a different SQL ...
    (comp.databases.ms-access)
  • Re: Crosstab REPORT, not query
    ... you can use the 'Database Tuning Advisor' against the SQL ... other books on ADP? ...
    (microsoft.public.access.adp.sqlserver)