# Excel import fails converting data version 5.2.1.299

**URL:** <https://forums.toadworld.com/t/excel-import-fails-converting-data-version-5-2-1-299/52712>\
**Category:** Toad Data Point & Toad Intelligence Central\
**Created:** [April 30, 2021, 9:23pm UTC](https://forums.toadworld.com/t/excel-import-fails-converting-data-version-5-2-1-299/52712 "2021-04-30T21:23:57Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pterobyte](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/pterobyte/32/13519_2.png) [@Pterobyte](https://forums.toadworld.com/u/Pterobyte)\
**Post date:** [April 30, 2021, 9:23pm UTC](https://forums.toadworld.com/t/excel-import-fails-converting-data-version-5-2-1-299/52712/1 "2021-04-30T21:23:57Z")

</div>

I'm running Toad Data Point 4.3.0.718 and cannot duplicate the problem my team is having with TDP 5.2.1.229.  
When we import an excel file with data type varchar to a column type varchar in MS SQL 2008 we get the error:

_"Conversion failed converting the **varchar** value 'blah blah' to data type **int**."_

They get this failure on both import to existing and import to new table. We are importing **nvarchar** to **nvarchar** and it thinks the destination is **int** when it is actually **nvarchar**.

They can make it work if they export to a .CSV file, but that adds steps. Our company no longer installs 4.3 so I can't install the older version for them. My version works even with formulas while the new version does not. We removed formulas, saved as xlsx, xls etc, Only CSV works for the newer version.

---

<div class="post-metadata">

**Author:** ![Gary.Jerep](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/gary.jerep/32/205_2.png) [@Gary.Jerep](https://forums.toadworld.com/u/Gary.Jerep)\
**Post date:** [May 17, 2021, 6:06pm UTC](https://forums.toadworld.com/t/excel-import-fails-converting-data-version-5-2-1-299/52712/2 "2021-05-17T18:06:23Z")

</div>

This looks like a bug... can you please open a Support ticket so that R&D can properly investigate and track?

---

<div class="post-metadata">

**Author:** ![mc2863](https://avatars.discourse-cdn.com/v4/letter/m/839c29/32.png) [@mc2863](https://forums.toadworld.com/u/mc2863)\
**Post date:** [November 28, 2021, 8:06pm UTC](https://forums.toadworld.com/t/excel-import-fails-converting-data-version-5-2-1-299/52712/3 "2021-11-28T20:06:38Z")

</div>

Hello. Has there been any resolution to this issue?

---

<div class="post-metadata">

**Author:** ![Julie\_Hyman](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/julie_hyman/32/13709_2.png) [@Julie\_Hyman](https://forums.toadworld.com/u/Julie_Hyman)\
**Post date:** [November 29, 2021, 5:23pm UTC](https://forums.toadworld.com/t/excel-import-fails-converting-data-version-5-2-1-299/52712/4 "2021-11-29T17:23:46Z")

</div>

I am trying to track down the support request but cannot find it and I don't have the support # that was opened. Are you encountering this issue in the latest product - Toad Data Point 5.5 ?

---

<div class="post-metadata">

**Author:** ![mc2863](https://avatars.discourse-cdn.com/v4/letter/m/839c29/32.png) [@mc2863](https://forums.toadworld.com/u/mc2863)\
**Post date:** [November 29, 2021, 7:18pm UTC](https://forums.toadworld.com/t/excel-import-fails-converting-data-version-5-2-1-299/52712/7 "2021-11-29T19:18:19Z")

</div>

Was able to get 5.5 sooner than expected, and yes I am still receving the same error. Table is created as varchar data type, but for some reason on import it is trying to convert it to int.

Conversion failed when converting the varchar value 'AB8717' to data type int.

---

<div class="post-metadata">

**Author:** ![Julie\_Hyman](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/julie_hyman/32/13709_2.png) [@Julie\_Hyman](https://forums.toadworld.com/u/Julie_Hyman)\
**Post date:** [December 9, 2021, 1:39pm UTC](https://forums.toadworld.com/t/excel-import-fails-converting-data-version-5-2-1-299/52712/8 "2021-12-09T13:39:34Z")

</div>

Is there a way you can sort the data so that the value 'AB8717' is within the first 10 being imported?

---

<div class="post-metadata">

**Author:** ![elena.saxton](https://avatars.discourse-cdn.com/v4/letter/e/b9bd4f/32.png) [@elena.saxton](https://forums.toadworld.com/u/elena.saxton)\
**Post date:** [February 3, 2023, 9:26pm UTC](https://forums.toadworld.com/t/excel-import-fails-converting-data-version-5-2-1-299/52712/9 "2023-02-03T21:26:05Z")

</div>

Has a resolution to this been found, it's very annoying. The only way I can get it to import is to put it in Access first...

---

<div class="post-metadata">

**Author:** ![SSH](https://avatars.discourse-cdn.com/v4/letter/s/7c8e57/32.png) [@SSH](https://forums.toadworld.com/u/SSH)\
**Post date:** [December 13, 2023, 6:14pm UTC](https://forums.toadworld.com/t/excel-import-fails-converting-data-version-5-2-1-299/52712/10 "2023-12-13T18:14:03Z")

</div>

I experienced this last week, so it seems to still be an issue. And Yes - I did try sorting data to begin with an alpha string. But still failed. Can someone from Quest advise if there is a workaround for this ?

Thanks!

FYI - my Toad Data Point version is 6.1.0.40 (64 bit)

---

<div class="post-metadata">

**Author:** ![dragan.ognjenovic](https://avatars.discourse-cdn.com/v4/letter/d/f17d59/32.png) [@dragan.ognjenovic](https://forums.toadworld.com/u/dragan.ognjenovic)\
**Post date:** [December 14, 2023, 7:14am UTC](https://forums.toadworld.com/t/excel-import-fails-converting-data-version-5-2-1-299/52712/11 "2023-12-14T07:14:51Z")

</div>

Can you please open a Support ticket so that R&D can properly investigate and track?

---

<div class="post-metadata">

**Author:** ![IT-Boie](https://avatars.discourse-cdn.com/v4/letter/i/48db29/32.png) [@IT-Boie](https://forums.toadworld.com/u/IT-Boie)\
**Post date:** [May 22, 2024, 9:17am UTC](https://forums.toadworld.com/t/excel-import-fails-converting-data-version-5-2-1-299/52712/12 "2024-05-22T09:17:45Z")

</div>

We are using Version "Toad for SQL Server Subscription" with Version Number 8.0.0.65 and we are facing the same issue while trying to import data in a existing table from .xlsx-File. Although the target column is set to nvarchar, the import wizard tries to convert the values of the excel-file into int. Therefore the import fails with an convertion error. Is there any official statement to this bug?

---

<div class="post-metadata">

**Author:** ![Julie\_Hyman](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/julie_hyman/32/13709_2.png) [@Julie\_Hyman](https://forums.toadworld.com/u/Julie_Hyman)\
**Post date:** [May 22, 2024, 6:50pm UTC](https://forums.toadworld.com/t/excel-import-fails-converting-data-version-5-2-1-299/52712/13 "2024-05-22T18:50:17Z")

</div>

Hi - this is a Toad Data Point forum, you will want to post in the Toad for SQL Server forum. But let me see if I can answer here as well....

If you are using the import wizard to import into a new table, what does the datatype show for the columns of the table you are creating?

 ![image](https://global.discourse-cdn.com/quest/original/3X/d/5/d5fffaafd3641a2168db1482a12f75e8e946de6e.png)

---

<div class="post-metadata">

**Author:** ![Michael.L.Gregory](https://avatars.discourse-cdn.com/v4/letter/m/ee7513/32.png) [@Michael.L.Gregory](https://forums.toadworld.com/u/Michael.L.Gregory)\
**Post date:** [October 18, 2024, 6:32pm UTC](https://forums.toadworld.com/t/excel-import-fails-converting-data-version-5-2-1-299/52712/14 "2024-10-18T18:32:11Z")

</div>

Has anyone found a way to resolve this? I'm using Toad Data Point 6.05.425 (64 bit) and still encountering this error.

---

<div class="post-metadata">

**Author:** ![Julie\_Hyman](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/julie_hyman/32/13709_2.png) [@Julie\_Hyman](https://forums.toadworld.com/u/Julie_Hyman)\
**Post date:** [December 3, 2024, 6:08pm UTC](https://forums.toadworld.com/t/excel-import-fails-converting-data-version-5-2-1-299/52712/15 "2024-12-03T18:08:55Z")

</div>

Hi Folks - has anyone opened a support ticket on this issue so I can track internally? [support.quest.com](http://support.quest.com)
