IssueWhen working with Text files, the following error might occur:
Alternatively, you might see unexpected nulls when viewing your underlying data.
Create a schema.ini file: You can create a standard schema.ini file that will tell Jet how to read the CSV file, regardless of the regional settings. First, include a line that defines the current decimal separator as used in the CSV. For example, if the CSV uses a period as a decimal separator, type “DecimalSymbol=.”. Then, save the schema.ini file in the same directory as the CSV file. For more information about the schema.ini file, go to the MSDN website: https://docs.microsoft.com/en-us/sql/odbc/microsoft/schema-ini-file-text-file-driver. Using the example above, the first two entries in your schema.ini file will look like the following:
Replace the decimal separator: Alternatively, replace the decimal separator in the CSV file with another character, such as a semicolon (;). To do this, use the find and replace feature in the text editor you use to open the CSV file, find all characters that are used as a decimal separator, such as a period, and replace with a semicolon.
Export the underlying data to Microsoft Excel or another data source: If the above two solutions do not work, consider exporting your data to another data source, such as Excel or SQL Server.