title: What does the setting WorkArounds2=8192 do on an ODBC connection?
body: <p>My company has a 3rd party application that runs on a <a href="http://www.progress.com/" rel="nofollow noreferrer">Progress</a> database.  I've been building an application on top of their database using an ODBC connection.</p>
  
  <p>One of the "quirks" of Progress is that it doesn't honor SQL column widths, so it will allow 100 characters in a column defined as a varchar(50).  When reading this data via ODBC, I get the following error:</p>
  
  <blockquote>
    <p>Column test_column in table
    PUB.test_table has value exceeding its
    max length or precision.</p>
  </blockquote>
  
  <p>The support techs at the company that build the application pointed me towards adding some work around flags in the registry for the ODBC connection, however, I can't find any documentation as to what these flags will do or what the possible values are.  The registry keys are</p>
  
  <blockquote>
    <p>KEY_CURRENT_USER->Software->ODBC->ODBC.INI->MyODBCConnectionName->WorkArounds
    KEY_CURRENT_USER->Software->ODBC->ODBC.INI->MyODBCConnectionName->WorkArounds2</p>
  </blockquote>
  
  <p>Google has found me other problems that people have solved by adding these flags with specific values (including my personal favourite from <a href="http://thedailywtf.com/Articles/Oh,_the_Workarounds.aspx" rel="nofollow noreferrer">The Daily WTF</a>) but I can't find anywhere that tells me what the flags actually do.  Do you know?</p>