Configurable exception throwing on parsing error

[jbezak]

We have a lot of cases where a high numeric value is stored in DBF which overflows the DBF limits. This is then stored as series of * and the library fails to read the record. In these case we would like to continue reading the DBF and display default value instead. This is also what DBF viewing tools are doing.

I made this configurable in NextRecord() method.

[jbtule]

I'm thinking about this.

Leaning towards accepting it. I just have to be careful, because it's a binary breaking change.

I'm weighing between uping the version number, or changing it to an overload. I have a general preference for optional params.

[jbezak]

I have no problem making it an optional param instead of overload.

Let me know your preference and I can get to this within a day or two.

[jbezak]

@jbtule I came across this pull request today after long time and changed it to optional param