#VALUE when importing
- VPillay1
- Topic Author
- Offline
- New Member
Less
More
9 years 8 months ago #1
by VPillay1
#VALUE when importing was created by VPillay1
Afternoon Ian,
When importing the ASCII file, any rates that have a value of R1000 or greater get carried across with the "," separator ie R1000.00 will be carried as R1,000.00 into excel.
The problem is that when the calculation is run for the total amount, an "Error in Value" occurs.
Is there any way to rectify this without re-entering the rates for these items again?
When importing the ASCII file, any rates that have a value of R1000 or greater get carried across with the "," separator ie R1000.00 will be carried as R1,000.00 into excel.
The problem is that when the calculation is run for the total amount, an "Error in Value" occurs.
Is there any way to rectify this without re-entering the rates for these items again?
Please Log in to join the conversation.
- Ian
- Offline
- Moderator
9 years 8 months ago - 9 years 8 months ago #2
by Ian
Replied by Ian on topic #VALUE when importing
Hi Vedarsharn,
I suspect that Excel may be seeing those values as text rather than numbers.
Assuming that this is the case, the article at office.microsoft.com/en-za/excel-help/co...ers-HP010342308.aspx provides step-by-step instructions on how to resolve this issue.
Please let me know how this works out for you.
Kind regards,
Ian
I suspect that Excel may be seeing those values as text rather than numbers.
Assuming that this is the case, the article at office.microsoft.com/en-za/excel-help/co...ers-HP010342308.aspx provides step-by-step instructions on how to resolve this issue.
Please let me know how this works out for you.
Kind regards,
Ian
Last edit: 9 years 8 months ago by Ian. Reason: Corrected hyperlink to article
Please Log in to join the conversation.
- VPillay1
- Topic Author
- Offline
- New Member
Less
More
9 years 8 months ago #3
by VPillay1
Replied by VPillay1 on topic #VALUE when importing
Afternoon Ian,
Thanks for the link. I had a look at the article, unfortunately none of the techniques listed helped.
I found a solution by changing the "Thousand Symbol" setting in WinQS from a comma to a space. Once that was changed, the values exported into excel as numbers and not text.
Thanks for your help and keep up the great work.
Thanks for the link. I had a look at the article, unfortunately none of the techniques listed helped.
I found a solution by changing the "Thousand Symbol" setting in WinQS from a comma to a space. Once that was changed, the values exported into excel as numbers and not text.
Thanks for your help and keep up the great work.
Please Log in to join the conversation.
- Ian
- Offline
- Moderator
9 years 8 months ago #4
by Ian
Replied by Ian on topic #VALUE when importing
Thank you for the update.
I will look into incorporating some sort of error checking for such cases in a future version.
Kind regards,
Ian
I will look into incorporating some sort of error checking for such cases in a future version.
Kind regards,
Ian
Please Log in to join the conversation.