Build, protect and deploy apps across any platform and mobile device
Leverage a complete UI toolbox for web, mobile and desktop development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Build mobile apps for iOS, Android and Windows Phone
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premise data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Automate decision processes with a no-code business rules engine
Many remember the fall of 1992 as the time when Super Mario Kart came out. Or when the World Wide Web was born. What many don’t remember, however, is that the ODBC driver was released in September of 1992. While it doesn't seem like an important milestone, database management systems (DBMS) would not be where they are today without this key driver. ODBC was developed by the SQL Access Group, a collection of software companies that included Microsoft, in order to standardize the use of DMBS by applications. Our own John Goodson was also heavily involved in the development, back in his Microsoft days. The driver works similarly to a printer driver, providing one central location from which an application can access information and standardize its use. In 1994, while most people were out seeing the Lion King or catching the first episode of Friends, ODBC developers were releasing version two of the driver. The second version reorganized the API core, made changes to level 1 and 2 conformance and input new data types. Only a year later, the same year that Windows 95 was released (and so was OJ Simpson), ODBC 3.0 was developed. This version introduced a larger number of new APIs and ODBC descriptor handles. Even though there have been many updates to ODBC since 1995, most Linux drivers and many applications use the ODBC 3.0 driver. When ODBC was developed no one could guess that it would become an integral API for today’s enterprise. Even twenty years later, developers frequently employ ODBC to tackle critical business challenges (such as Big Data, cloud computing and mobile computing), and in August of last year, Microsoft officially announced that it was fully focusing its resources and development on the ODBC standard for all its native client applications. And as version 7.0 of the driver was released earlier this year, it’s becoming even more evident that ODBC will be sticking around for a while! Tune in for our next post where we look at how ODBC continued to develop from 1995 to the present. ?Image sourced from http://gamrfeed.vgchartz.com/galleries/2011-07-04/evolution-of-a-series-mario-kart/evolution-of-a-series-mario-kart_1309813288.jpg?sfdcid=701a0000002MkKS&cmpid=ddblog
View all posts from Paul Griffin on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2017, Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.