data connector sql server
ADD SQL SERVER AS A DATA CONNECTOR - The Access team is currently evaluating the use of data connectors in Access, (https://youtu.be/j5UAv4yY5RY?t=2155), and we need your support to get them to include SQL Server as an option! PLEASE VOTE for this idea, every vote counts!
Frank Rotolo commented
If you want to use ADP again, use Access 2010. Microsoft has no intentions of bringing ADP back in newer versions.
We are in end of July
Four month and no single comment from microsoft
This tells you how serious they are listening to customers
This is by far the top voted item and they are ignoring it
Don't you guys get it
This product has zero segnifcant updates for 10 years
They have no intention of doing nothing
They are fony
Rene Hug commented
Bring back ADP or something that allows me to use Access as front-end as easy as with ADP! The majority of solutions I have to provide to business are internal and never ever will be put into a cloud. Ease of build is much more important for me than using the whole technology stack of a Web Application!
Got the feeling, MS-Access-policy has now a wrong direction: please maximize Access, not minimize it. Otherwise it's getting too foggy in the clouds.
I'll add my thought to this message black hole that no one at MS will ever read. It was irresponsible to remove ADP functionality with out a viable replacement that had equivalent functionality and ease of use.
Daniel chen commented
The sad part is, we do not see any comments from Microsoft
now that the "Access web application" is officially dead the objection to this type of connection is gone
Microsoft must do the following
1. bring back the ADP functionality - the sql connections parts - Should be there, it is just disabled!!!
2. the next thing to focus on is - convert access to vb.net and give us functionality like the new windows forms, IE XAML and disconnected adodb.net
to simply put it - bring back ADP!!!!
1. single connection that expose entire schema
2. "Server Filters" - reduce network traffic by a factor of a 1000
3. all SQL objects are available for consumption by forms and reports
4. scalability is close to unlimited
5. use of stored procedures is a snap
6. slap few new components like VS
we can do all the rest and you get your glory that you lost with the crippled access web App
PJ Bryant commented
I've just had to start an ADP to Access 2016 project. It hurts. This is bleeding obvious it's astonishing Microsoft removed it, let alone have to ask if we want it back. Easily leveraging the backend power is just necessary.
Moshe Arzt commented
with these data connectors, how to link to tables/objects with more than 255 columns?
I had a problem with this while using a commercially available ODBC driver to link to Salesforce tables. A few tables/objects had over 255 fields, and the Access link simply truncated at the 256th field.
Detlef Traum commented
I agree with all other posts: Since adp is gone, i work only with ACC 2010 because i would have to invest thousands of hours to bring my application (Developement since 2003) to ACCDB. So much time... incredible costs for what? One step back in performance and function? Please do something equivalent to ADP
Sigurd Aas commented
@Juan: "Please provide a great example of how you used SQL Server with Access":
My Company uses Access as frontend for SQL server in a ERP type solution.
Among many things, we support truck tablets With our software running on Access clients connecting over wifi. SQL server is a must when supporting difficult environments like wifi connections.
If this request eliminates some of the DAO/ADO (e.g. make DAO support disconnected recordsets, upload BLOB data, etc), it would be very useful
Bob Alston commented
SQL server as a data connector for Access would be very helpful! Please!
Bernd Rudolf commented
ohne ADP wäre ich nicht mehr arbeitsfähig.
Deshalb bleiben wir aktuell so lange auf Access 2010 bis es irgendwas vergleichbares gibt.
Cesar Gonzalez commented
SQL's powerful and speedy back end, with Access's flexible front end UI, has allowed us to make continual and rapid deployments to our application to audit our always changing client data.
Matthias R. commented
Wir arbeiten mit vielen Access-Frontends auf dem SQL-Server - bis zur Umstellung auf Office 2016 oft mit ADP-Dateien. Es wäre toll, wenn ein direkter Data-Connector vorhanden wäre.
Dieter Esser commented
Das wäre super, wenn es das gäbe
Ursula Fehn commented
I fully support Klemens Konopasek' s comment to ADP.
To adapt all running ADP applications is very cost intensive and nobody will pay for as there is no additional benefit to our customers
Klemens Konopasek commented
Since ADP disappeared with Access 2013, I'm waiting for a proper alternative. Access has been a magnific frontend for SQL Server, now it is just a good one. You see what you've lost, when you try to migrate an ADP to an ACCDB. There's so much functionality lost you had before. We need direct binduing of SQL (SQL Server Syntax, no linked Tables with Acccess-Syntax) to forms and reports again with support of ALL SQL Server object-types.
I need a proper replacement for ADP, for all the Solutions I've developed in the past. One cannot redevelop all the solutions, he developed in the past years since 1999 - nobody would pay for that.
From my point of view there is nothing more needed in Access than that ...
Please take ADP, replace OLE-DB by ODBC and give it back to us. :-)
Michael Simcich commented
As far as apps built with Access front ends connected to SQL Server, that's the normal platform for the work I do at AccessTools.com. Types of applications to date include:
Teleradiology Workflow Solution
Medication Reconciliation software for an HMO
Inventory Managment with eBay interface
Risk Management software
and lots of others. Access is a great front end to SQL Server, but having a more transparent connection to SQL Server would be great.