<P> ODBC remains in wide use today, with drivers available for most platforms and most databases . It is not uncommon to find ODBC drivers for database engines that are meant to be embedded, like SQLite, as a way to allow existing tools to act as front - ends to these engines for testing and debugging . </P> <P> However, the rise of thin client computing using HTML as an intermediate format has reduced the need for ODBC . Many web development platforms contain direct links to target databases--MySQL being very common . In these scenarios, there is no direct client - side access nor multiple client software systems to support; everything goes through the programmer - supplied HTML application . The virtualization that ODBC offers is no longer a strong requirement, and development of ODBC is no longer as active as it once was . </P> <P> Version history: </P> <Ul> <Li> 1.0: released in September 1992 </Li> <Li> 2.0: c. 1994 </Li> <Li> 2.5 </Li> <Li> 3.0: c. 1995, John Goodson of Intersolv and Frank Pellow and Paul Cotton of IBM provided significant input to ODBC 3.0 </Li> <Li> 3.5: c. 1997 </Li> <Li> 3.8: c. 2009, with Windows 7 </Li> <Li> 4.0: Development announced June 2016 with draft spec on Github </Li> </Ul>

What is odbc compliance and also explain export and import