ETL and Data Integration tools - Modern ETL software for everyone

Hello,

I am a newbie evaluating the currently downloadable version of VI for use in importing a hundred or so similarly formatted excel files into MS Access. I am having trouble mapping the fields in the input excel file to the output which is MS Access via ODBC. I have reviewed the available tutorials on your website, the VI user guide (pdf), and also your support forums and have not been able to identify a solution with my limited knowledge.

The fields appear to be mapped correctly in the UI and in the associated .vis file. However, when I do a data preview, or run the actual extract, the fields are not actually mapped and the data does not come through.

I have sent you a set of files you can use to replicate -- the .vis file, the test input file, the test output file, and a screenshot of the VI UI showing the fields correctly mapped (I think) and also the data preview grid showing the fields not correctly mapped.

I have no doubt this is some sort of user set up problem but I have not been able to identify it .... help/suggestions welcome. I have been writing, and maintaining, VB, DTS scripts etc for years to solve this need and I believe VI will significantly simplify the task and reduce the ongoing maintenance - if I can just solve this issue.

Thanks in advance.

-- Scott

In the access file you sent us every single field has got a space at the end

This sql does work

Select
tmp_CONSOL.[Policy Contract ],
tmp_CONSOL.[Plan Code ],
tmp_CONSOL.[Policy Type ],
tmp_CONSOL.[Assoc# No# ]
From
tmp_CONSOL

this does not

Select
tmp_CONSOL.[Policy Contract],
tmp_CONSOL.[Plan Code],
tmp_CONSOL.[Policy Type],
tmp_CONSOL.[Assoc# No#]
From
tmp_CONSOL

That makes it very difficult to work with your file.
We have made some changes and the latest version of visual importer etl actually does work with it.
Please try it and let us know the outcome

Mike

Mike,

A subtle problem and not a trivial one to troubleshoot. I will:

1. Check again with the latest version of VI and verify the resolution with you
2. Then eliminate all special and nonprintable characters in the field names of the destination file.

Thanks to you and the team at dbsoftlab for the analysis and the very quick turnaround.

I will be back to you within 24 hours on point 1 above.

Scott

Mike,

I downloaded VI v4.9.8.2 and verified that it correctly handles the problem – both with, and without, the trailing spaces.
I believe at this point that VI will handle 100% of our need and your sales team should see an order in the near future.

Kudos for the great support work, it has been quite some time since I have dealt with a software support group demonstrating such a high level of responsiveness/effectiveness.

Best regards,
Scott