Home |
Search |
Today's Posts |
|
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Hi Nicke,
We track the issue following the email you registered in the MSDN database. In this way, each MSDN subscriber's post will be checked by Microsoft support professional. For this issue, I'd suggest you can check the regional setting from control panel (start-Control Panel-Regional and language options ). Is there any difference of the setting in the box Excel 2003 installed from the one Excel 2000 or 2002 installed? My regional setting is English(united states) and the output in my Excel 2003 is "123,456" after the execution of your vba code. Please feel free to let me know if you have any further questions. Does this answer your question? Thank you for using Microsoft NewsGroup! Wei-Dong Xu Microsoft Product Support Services Get Secure! - www.microsoft.com/security This posting is provided "AS IS" with no warranties, and confers no rights. |
#2
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Hi,
Thank you for your answer, here is my response. Yes I tried to changed to English (USA) and got 123,456, my (and my clients) settings is Svenska or Swedish. The problem is that here in Sweden we have a comma (",") for a decimal separator and space for thousand separator. When I switched to English I got 123,456 but what I try to put in the cell is (in your language) 123.456 (less than 124, hope you understand). It seems like Intersect always want a period as a comma (it don't care about the national settings) because if I change the code to Arr(0,0) = "123.345", and have comma as a delimiter, it interpret the period as a comma and put the right value in the cell. This was discovered when a client had changed to Excel 2003 and got too large values in my program and when I debugged my program I noticed this behaviour in Excel 2003. I hope you can confirm this behaviour and possible help me with a workaround. Thanks in advance. /Nicke -----Ursprungligt meddelande----- Hi Nicke, We track the issue following the email you registered in the MSDN database. In this way, each MSDN subscriber's post will be checked by Microsoft support professional. For this issue, I'd suggest you can check the regional setting from control panel (start-Control Panel- Regional and language options ). Is there any difference of the setting in the box Excel 2003 installed from the one Excel 2000 or 2002 installed? My regional setting is English(united states) and the output in my Excel 2003 is "123,456" after the execution of your vba code. Please feel free to let me know if you have any further questions. Does this answer your question? Thank you for using Microsoft NewsGroup! Wei-Dong Xu Microsoft Product Support Services Get Secure! - www.microsoft.com/security This posting is provided "AS IS" with no warranties, and confers no rights. . |
#3
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Hi Nicke,
Thank you for replying! So far as I know, intersect is working following the regional settings. If you set the language to Swidesh, "123.345" will be displayed in "123" in the cell(1, 1) with intersect. If you set the regional setting to Chinese(PRC), it is also the same. However, the "123,345" can be displayed very normally in Chinese(PRC) which is not the same to "123 345" in Swidesh. From my experience, you can add one '#' before the data "123,345". In this woraround, intersect will not change the "123,345" to "123 345". Please note you will need to remove the '#' before you use the value. Please feel free to let me know if you have any further questions. Does this answer your question? Thank you for using Microsoft NewsGroup! Wei-Dong Xu Microsoft Product Support Services Get Secure! - www.microsoft.com/security This posting is provided "AS IS" with no warranties, and confers no rights. |
#4
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Hi, thank you for your answer.
OK, I think I know whats going on here... My array contain "123,456" but obviously you must have "123.456" to use intersect. "123,456" returns "123 456" which is 1000 times bigger than "123,456" (in Sweden). "123.456" returns "123,456". Why I don't have recognized this before is that "123,45" returns "123,45" (formated as text though). The result is wrong when there is more than 2 decimals. So I guess I have to change my program to replace the comma with period. /Nicke -----Ursprungligt meddelande----- Hi Nicke, Thank you for replying! So far as I know, intersect is working following the regional settings. If you set the language to Swidesh, "123.345" will be displayed in "123" in the cell(1, 1) with intersect. If you set the regional setting to Chinese(PRC), it is also the same. However, the "123,345" can be displayed very normally in Chinese(PRC) which is not the same to "123 345" in Swidesh. From my experience, you can add one '#' before the data "123,345". In this woraround, intersect will not change the "123,345" to "123 345". Please note you will need to remove the '#' before you use the value. Please feel free to let me know if you have any further questions. Does this answer your question? Thank you for using Microsoft NewsGroup! Wei-Dong Xu Microsoft Product Support Services Get Secure! - www.microsoft.com/security This posting is provided "AS IS" with no warranties, and confers no rights. . |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Link to Help topic? | Excel Discussion (Misc queries) | |||
How is a a help topic example selected? | Excel Discussion (Misc queries) | |||
Topic did not show up? | Excel Worksheet Functions | |||
example in the help topic | New Users to Excel | |||
Off Topic Messages | Excel Worksheet Functions |