RE: Table ranges do not work in multilingual configurations

Dear Jialiang,

Thank you for your prompt response. You have understood the problem
correctly, however the analogy with Sheet1/Tabelle1 does not apply to my
case. The problem with the keyword #All is very special and unique.

When you create a workbook in the German version of Microsoft Office, the
default ID of the first *** is "Tabelle1". You could as well choose an ID
manually, Tabelle1 is just a default value. Let's suppose you don't change
the default value: If you open the workbook in another UI language, you can
still refer to it as Sheets("Tabelle1"). Thus, there isn't any problem with
the keywords Tabelle1/Sheet1. To reproduce this behavior:

1- Create an Excel workbook in the German version of Microsoft Office.
2- Write the following code:

Private Sub Workbook_Open()
ThisWorkbook.Sheets("Tabelle1").Cells(1, 1) = "test"
End Sub

3- Close Excel, switch the UI to English, reopen the same workbook, the VBA
code will work flawlessly.

That's not the case with the keyword #All. You can think of "Table1[#All]"
as the ID of the table. Thus, it is as if the ID of the table changes when
the user switches the UI language.

I would be very glad if you could find a workaround for it in Pivot Tables.

Sincerely.
Elyo Ravuna

"Jialiang Ge [MSFT]" wrote:

Hello Elyo,

From your post, my understanding on this issue is: you wonder how to make a
pivot table compatible with all language versions of Office 2007. If I'm
off base, please feel free to let me know.

I reproduced the issue by following your steps. In Office 2007 with French
Language Pack, it would expect " [#Tout]" rather than " [#All]". As you
said, the difference of the keyword [#All] makes the error. I am now
consulting Excel Product team, to see if there is a method to make a pivot
table compatible with different Office Language Packs. I will get back to
you as soon as possible.

Actually, almost all the other Office application have similar strings that
change between languages. The overall recommendation would be to stay away
from these strings and use ID to access the objects. For example, in the
English version of Excel, you have Sheet1, Sheet2, etc. in German they are
named Tabelle1, Tabelle2, etc. If you use something like Sheets("Sheet1")
in combination with the German version, it will fail. But we could use
Sheets(1) to avoid the problem. I need to consult Excel product team to see
if there is a similar workaround for it in Pivot Table.

Sincerely,
Jialiang Ge (jialge@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support

==================================================
For MSDN subscribers whose posts are left unanswered, please check this
document: http://blogs.msdn.com/msdnts/pages/postingAlias.aspx

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications. If you are using Outlook Express/Windows Mail, please make sure
you clear the check box "Tools/Options/Read: Get 300 headers at a time" to
see your reply promptly.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


.