 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Multiuser / Networking / June 2005Future of ADPs?
Does anyone know what the future plans are for ADPs? Will they continue to be supported by MS for SQLServer 2005? I have heard disturbing rumours that MS have no plans to develop ADPs further... anyone have any insight? We've made big investments into ADP front-ends to SQLServer and continue to do so... if they're dropping support we need to do a rethink soon. > Does anyone know what the future plans are for ADPs? Will they continue to be > supported by MS for SQLServer 2005? I have heard disturbing rumours that MS > have no plans to develop ADPs further... anyone have any insight? > We've made big investments into ADP front-ends to SQLServer and continue to > do so... if they're dropping support we need to do a rethink soon. Why?  SignatureI don't check the Email account attached to this message. Send instead to... RBrandt at Hunter dot com Why would we need a rethink? I don't pretend to know much about all the issues but let me ramble on a bit to explain how ADPs fit in for us: We have decided to SQLServer 2005 (from 2000) as soon as it becomes available for a whole variety of reasons. We have tried to use ADPs to connect to our migrated 2000 database in native SQLServer 2005 (beta 2) mode (not SQLServer 2000 compatibility mode) and they don't work. We went to ADPs because they were a great deal more efficient/fast than MDB implementations, and easier to develop with SQLServer 2000. MDBs were too slow and one really had to code tightly to avoid big performance problems. I've seen lots of people talk about "efficiently designed" MDBs with linked tables, but you have to jump through hoops to avoid performance problems. ADPs provided neat little gizmos like ServerFilters and others to vastly improve performance as well as better support for server-side sp, functions etc. The developers also much preferred ADPs because they provided a single development environment - and graphical function/sp development. The Access front-ends are only one of the interfaces to our SQLServer databases - the others are all .Net-based: Asp.Net 2.0 web, webservices, and some VB.Net applications. We've preferred using Access ADPs for the back-office because they have been a very quick and efficient tool to develop in. We have been able to offer the Access ADPs very well to other offices via Terminal Services. Most of our SQLServer development is done in an ADP (graphical interfaces for functions, sps, etc. are great). However, if ADPs aren't going to be supported properly, and won't support at least what was supported with SQLServer 2000, there seems little point investing in them. I just want to understand if ADPs are being dropped from Microsoft's plans (and thus whether we should look at converting our ADPs to MDBs - unlikely, or dumping Access altogether and moving towards VB.Net interfaces for our back-offices). As we are starting a relatively big development project now, I want to know whether ADPs are going to remain a good solution. > > Does anyone know what the future plans are for ADPs? Will they continue to be > > supported by MS for SQLServer 2005? I have heard disturbing rumours that MS [quoted text clipped - 3 lines] > > Why? To the best of my knowledge, Microsoft have made no public announcement on the future of ADPs. When you're not sure where something is going, the best you can do is to look at where it is coming from. Ask yourself "how many ADP-specific features where added or improved in Access 2002 and Access 2003?" and plan accordingly. SignatureBrendan Reynolds (MVP) > Why would we need a rethink? I don't pretend to know much about all the > issues but let me ramble on a bit to explain how ADPs fit in for us: [quoted text clipped - 48 lines] >> >> Why? > To the best of my knowledge, Microsoft > have made no public announcement on [quoted text clipped - 5 lines] > Access 2002 and Access 2003?" and > plan accordingly. The OP might also want to consider that the Microsoft Product Manager who was in charge of ADP in Access 2002 has recently said that MDB-Jet-ODBC-SQLServer is currently to be preferred over ADP-ADODB-OLEDB-SQL Server for implementing Access clients to SQL Server databases. In my limited work with ADPs, I did not run into any insurmountable difficulties, but didn't find them as "great" as the OP seems to believe. In fact, I came away with the answer "No, not unless external forces require that they do." to my question "Is it worth the time and effort for experienced Access developers to learn ADP?" I suspect the differences due to architecture, design, and implementation of a given application have far more to do with the ease of implementing it and the speed and stability of the production database than the specific Access approach used. I've been waiting for Don P Mellon (under whatever alias he is using today) to do some rigorous performance comparisons -- he complained about my not doing so, and, thus, inherited that responsibility. Alas, Don seems to have other tasks of higher priority to keep him occupied. Larry Linson Microsoft Access MVP I'd believe the rumours about limiting development. MS might not have said it 'publically' but I've attended meetings where they have said it (and the same about Data Access Pages) and these were not 'private' meetings. 'Support' is an entirely different question . The rumour that I have heard, which I cannot get confirmed or denied is that we have an update to Jet on the way. Peter > Does anyone know what the future plans are for ADPs? Will they continue to > be [quoted text clipped - 4 lines] > to > do so... if they're dropping support we need to do a rethink soon. >Does anyone know what the future plans are for ADPs? Will they continue to be >supported by MS for SQLServer 2005? I have heard disturbing rumours that MS >have no plans to develop ADPs further... anyone have any insight? >We've made big investments into ADP front-ends to SQLServer and continue to >do so... if they're dropping support we need to do a rethink soon. Well the improvements MS have made to the core Access product that I use every day hasn't been that significant since A97. Sure, there's ADO but that's not a big deal to me. There are some nice new features but nothing earth shattering. That said MS haven't dropped any features either. DAPs to my knowledge work just fine. Although very few people are using them. So I would then suspect that ADPs will continue to work just fine. Whether they will work just fine against SQL Server 2005 I do not know. I suspect they will just because SQL Server 2005 will be out this year and Office Next will be out after that. I'm sure others will have the same concerns as you. And these others are likely to be the enterprise type of customers with more pull than smaller customers. But I certainly can't guarantee anything. Tony SignatureTony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.