Text file Data Source - Insight 1.0.1
Hello All,
I am trying to setup a data source to be used in Insight 1.0.1. The file is of csv format but it has a .log extension that I cannot change.
I know how to connect to a .csv file, but the same steps fail for the .log file. Does anyone know if there is a trick in order to make this work?
Thank you!
Nataliya
I am trying to setup a data source to be used in Insight 1.0.1. The file is of csv format but it has a .log extension that I cannot change.
I know how to connect to a .csv file, but the same steps fail for the .log file. Does anyone know if there is a trick in order to make this work?
Thank you!
Nataliya
2 answers
Hello Jeff,
Thank you for replying!
Let me try to describe it in details:
When I create the data source for the csv file I follow those steps:
1. Open ODBC Admin and create a new System Data Source with the Microsoft Text Driver.
2. In the Setup dialog, specify the directory where my file is located. Click on Options button.
3. Select my extension (.csv or .txt ) from the list of available formats and click on Define Format button.
4. In the Define Text Format dialog I select my file name, and define columns names by specifying their Data Type, Name and Width. Check or Uncheck the Column Name Header checkbox depending on the file structure.
5. Save everything and exit ODBC Admin.
6. Create a new Data Source in the Data Manager and point it to my new ODBC System Data Source.
7. Open SQL term and validate that I can select the data.
These steps works for txt and csv. However I have a .log file and the here is the issue:
At the step 3 - there is no .log extension defined. So I click on the Add button to add it. After that I go through steps 4-5. However at some point I get this error: Invalid setting in Excel key of the Engines section of the Windows Registry. And after that the list of the available extensions becomes corrupted and I have to clear it by clicking the Default checkbox. In the SQL term, I can see the file but I cannot get the data.
I searched for this error message but I couldn't find any answers.
It is highly desirable that I don't change the extension of my data file. I'd like to connect to it directly instead of copying it and renaming it. The file is rather large and any manual intervention is to be avoided...
Let me know what you think about all of this! Thanks again for your help!
You can try this with any .log file. I am sure you will run into the same issue...
Nataliya
Thank you for replying!
Let me try to describe it in details:
When I create the data source for the csv file I follow those steps:
1. Open ODBC Admin and create a new System Data Source with the Microsoft Text Driver.
2. In the Setup dialog, specify the directory where my file is located. Click on Options button.
3. Select my extension (.csv or .txt ) from the list of available formats and click on Define Format button.
4. In the Define Text Format dialog I select my file name, and define columns names by specifying their Data Type, Name and Width. Check or Uncheck the Column Name Header checkbox depending on the file structure.
5. Save everything and exit ODBC Admin.
6. Create a new Data Source in the Data Manager and point it to my new ODBC System Data Source.
7. Open SQL term and validate that I can select the data.
These steps works for txt and csv. However I have a .log file and the here is the issue:
At the step 3 - there is no .log extension defined. So I click on the Add button to add it. After that I go through steps 4-5. However at some point I get this error: Invalid setting in Excel key of the Engines section of the Windows Registry. And after that the list of the available extensions becomes corrupted and I have to clear it by clicking the Default checkbox. In the SQL term, I can see the file but I cannot get the data.
I searched for this error message but I couldn't find any answers.
It is highly desirable that I don't change the extension of my data file. I'd like to connect to it directly instead of copying it and renaming it. The file is rather large and any manual intervention is to be avoided...
Let me know what you think about all of this! Thanks again for your help!
You can try this with any .log file. I am sure you will run into the same issue...
Nataliya