title: Creating a custom ODBC driver
body: <p>At my current job, we're looking to implement our own odbc driver to allow many different applications to be able to connect to our own app as a datasource. Right now we are trying to weigh the options of developing our own driver to the implementation spec, which is massive, <em>or</em> using an SDK that allows for programmers to 'fill in' the data specific parts and allow higher levels of abstraction.</p>
  
  <p>Has anyone else implemented a custom odbc driver? What pitfalls did you run into? What benefits did you see from doing it yourself? How many manhours would you approximate it took? Did you use an SDK, and if so, what benefits/downsides did you see from that approach?</p>
  
  <p>Any comments and answers would be greatly appreciated. Thanks!</p>
  
  <p><strong>EDIT:</strong> We are trying to maintain portability with our code, which is written in C.</p>