Simba sells various kinds of data access Software Development Kits (SDKs). You might ask why; doesn't data always come with a programmatic way to get at it? Well, yes and no.
Our SDKs allow companies with unique or proprietary data stores to get the data out to standard client applications like MS-Excel, Crystal Reports, and MS-Access. Our various SDK customers know their data stores well, and how to access them programmatically. So they are the right group to implement a driver. However, they may not be experts in data access standards like ODBC, JDBC, and ADO.NET, nor SQL engine design. So the perfect solution to this perfect storm of data and APIs is to provide an SDK that contains all the standards-based code, and let them tack on the simple, custom back-end of the driver.
Here's a classic case. Bentley Systems is a global leader in providing comprehensive software solutions for maintaining infrastructure systems. Much of their data is stored in special file formats shared by various industry components. However, their customers often need to get data out into Excel or other client apps for further analysis or presentation. Bentley recently announced several new aspects to their solution, and in the second paragraph here their CEO, Greg Bentley, describes the classic 'trapped data' case.
I also liked how their CEO indicated that end customers also needed to get the data out and moved "onward to enterprise systems". This echos what I have said in a previous blog that drivers are not just needed for the client-app-to-database case, but also upstream app to downstream app.
Our SimbaEngine SDK played a key role in one aspect of the Bentley announcement. They needed an ODBC driver to access a special back-end data store via the C# programming language. Do you have 'trapped data', or an upstream system that needs operational flow to downstream systems? If so, check out SimbaEngine SDK and the many data access standards and back-end programming languages that we support.