I find it completely unaccepable that Adobe would discontinue ADBC. Years ago they sold it as the enterprise solution for commenting repositories. Now if I switch and get thousands of people using another solution...How long will it be before they decide to discontinue that? They obviously are not aware that large corporations can not just change on their whim. Some of their other solutions I have no access to. Perhaps it is time to start looking at their competition. I have always championed Acrobat at my company. If I push in another direction it will be the loss of thousands of licenses. You did it to yourself Adobe.
I hope everyone who misses ADBC will chime in on this to show their discontent as well. We build a solution around their product and they have nothing better to do than to break it.
I agree that it's a real shame that ADBC support was dropped from Acrobat.
However, it was not a complete surprise. Adobe deprecated this feature
during several iterations of Acrobat. In Acrobat 9 you actually had to
manually enable it in the registry to get it working.
So I would say that any corporation should have had enough time to adjust
their workflows to this change.
Still, I think it should have been left in the application, even just for
backwards-compatibility and because it can be so useful.
As try67 says, ADBC was removed very gradually so users had plenty of time to alter their workflows. Even when it was supported, a lot of people had problems getting it to work properly.
Adobe recommends that users who wish to implement database connectivity use XFA (via LiveCycle Designer) - not only is it easier to set up, but the forms will work in Adobe Reader. ADBC was always an Acrobat-only function.
Dave Merchant wrote:
Adobe recommends that users who wish to implement database connectivity use XFA (via LiveCycle Designer) - not only is it easier to set up, but the forms will work in Adobe Reader. ADBC was always an Acrobat-only function.
Just to clarify a bit, such forms can only work in Reader if the corresponding usage rights have been applied by LiveCycle Reader Extensions.
North America
Europe, Middle East and Africa
Asia Pacific