This usually indicates bad data in a date field. 

This is a VERY large file.  How do I go about finding the bad data in a date field?  I rebuilt the file in a test company and get the same results.

There are various tricks to find bad dates in ProvideX data, but I use ODBCView (3rd party software) and run a select * from ... query on the table.  When it errors out, you can often determine the offending line by the last one listed in the results.  DFDM to fix.  When the select query runs without errors, all dates are valid.

I got this error when using ADO.NET to connecting to the ProvideX ODBC driver.  The code was depending on connection pooling.  The code was connecting and disconnecting on every query.  It was slow, and also I think the ProvideX ODBC driver may not support connection pooling.  So after about 30 queries, I got this error on every subsequent query until the program quit.  I think the ProvideX ODBC driver hit a connection limit.  I change the code to open the ProvideX ODBC once at the beginning of the program and close it at the end, and the error went away.

David Nelson
Dynamic Enterprise Technologies Inc
Seattle Washington USA

I am again getting this error and cannot resolve it.  I do not understand how you changed the code in Access to open the ProvideX ODBC once at the beginning of the program and close it at the end as you describe your solution.

How did you do that to get the queries to work?