Driver Limitations

  • Thread starter Thread starter RS
  • Start date Start date
R

RS

Are there any limitations for Microsoft OLEDB text driver. I use Schema .ini
file to specify the columns. I have 280 columns in my schema file. Due to
the nature of the business that I am in I have to have dataset with that
number of columns. I get an error that says "Record is too large" If i only
leave 255 columns it works just fine. Is 255 a column limit?
 
¤ Are there any limitations for Microsoft OLEDB text driver. I use Schema .ini
¤ file to specify the columns. I have 280 columns in my schema file. Due to
¤ the nature of the business that I am in I have to have dataset with that
¤ number of columns. I get an error that says "Record is too large" If i only
¤ leave 255 columns it works just fine. Is 255 a column limit?
¤

This is a limitation of the Jet database engine which is used in conjunction with the Text ISAM
driver.

You may need to combine some of the fields and then split them apart once in a DataTable,
DataReader, etc.

The only other option I can think of is two split the Text file into two files, create two separate
queries to pull the data into two DataTables, and then create a DataRelation between the two
DataTables.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

The data in a linked Excel spreadsheet column is truncated to 255 characters in an Access database 0
reading text file using OLEDB into dataset 5
DataSet WriteXML empty fields /columns 1
DataColumn.Min/MaxLength 6
What sort of dataset is it? 3
Dataset column Names 1
Import Excel with more than 255 columns 1
CHECK constraint in .NET framework 1

Back
Top