Hi All,
I get the following error message when I try to download an Append Query to a blank workbook.
The Column '#' of the table wasn't found.
There is a column named "#"," but I changed the name to "Number" and I still get the same error message.
I can see the appended columns in Power Query, but when I try to download it to the workbook, I get the error message.
I even deleted the "#" column, and still get the error message. The odd thing is that the first time I downloaded it, it worked(appended 13 queries). The only problem I can see is that I get a message that my dictation program (Dragon Dictate) interferes with Power Query, but I am not using it now.
What am I doing wrong?
Cedric McKeever
Hi Cedric,
It's difficult to say without seeing the file. When you change a column name you must do it at the last step in case it is referred to elsewhere. The error implies that something is looking for this column, however it's odd that you can see the data in the Query Editor.
Can you try loading the query on a PC that doesn't have the dictation program? Even if it's not on it might be running in the background.
Mynda
First let me thank Mynda for taking time to answer my problem.
With that being said, I think I have found the problem. What I am doing is downloading horse racing entries. Let’s say there are eight horse running and there are eight races. Thus, there would be tables 0 to 7.
When I download these tables in the morning, transform them to the format I need, and append them, everything works fine. However, in the afternoon they add two tables for each race, one on how the horses finish and another on the payouts. The new tables are then listed in numerical order, 0, 1, 10, 11, etc. They also have different headings. The heading in the first tables “#” is not in the new tables.
I am wondering if the additional tables and the fact that the tables are no longer listed in the original order, and the headings are different, are confusing Power Query.
I tried it today, in the morning it worked, in the afternoon I got the same message.
Yes, I agree that this is the likely culprit, Cedric.
