Locale Identifier and serverside execution

Discussion in 'microsoft.public.sqlserver.olap' started by Lutz Morrien, Feb 17, 2004.

  1. Lutz Morrien

    Lutz Morrien Guest

    Hi all,
    I have not been here for a while since my field of work
    shifted somewhat awany from Analysis Services...

    Anyway: Using Excel 2002 as frontend, we are using server
    side execution by altering the connection string of the
    pivot table (transferring file into xml and back to xls)

    Settings added are ("Execution Location=3;Default
    Isonaltion Mode=1;Locale Identifier=1033").
    I added the locale for the AS server is an english
    installation and the Excel Client is a german

    And it does work. All work shifted to the server. Or
    better it did:
    When a pivot table or a worksheet or document containing
    a pt is copied into a new document, the locale id is lost.

    For some reason Excel also removes the locale identifier
    when a query was issued. Has anyone experienced this?

    Is there a workaround?

    TIA, Lutz Morrien
    Lutz Morrien, Feb 17, 2004
    1. Advertisements

  2. Hi Lutz,

    How did you set the connection string for this new excel sheet , you must
    edit the Microsoft Excel OLAP Query File (.OQY). By default, the Microsoft
    Excel OLAP Query File is stored in the C:\Documents and
    Settings\<User>\Application Data\Microsoft\Queries folder.


    "This posting is provided "AS IS" with no warranties, and confers no
    Bas Kersten [MSFT], Feb 18, 2004
    1. Advertisements

  3. Lutz Morrien

    Lutz Morrien Guest

    Hi Bas,
    thank you for responding on the issue.
    As far as I know, there are two methods of (re)setting
    the connection string in an excel worksheet.
    a) using the oqy created by Excel (a text file really)
    b) saving the Excel sheet as xml, editing the
    <connection> tag and saving the whole thing as xls again.

    (the oqy file is only used once by Excel, when a new
    pivot table is inserted. Excel stores a copy of the
    contained connection string in the excel sheet itself)

    We tried both, but either way, the Locale Identifier we
    set first exists and then is lost somehow. Which in turn
    results in the client side queries we wish to avoid. In
    contrary, the settings Execution Location=3 and Default
    Isolation Mode=1 remain in the connection string.

    Sounds like the only solution to this is using operation
    systems with identical language versions for the server
    and for all clients. (i.e. english server and english
    In this specific case, according to our experiences,
    adding Locale Identifier is be unnecessary.

    The only problem being that we have to either reinstall
    the server (or all clients) from scratch. ;(

    Any other hint on the issue?

    TIA Lutz Morrien
    Lutz Morrien, Feb 18, 2004
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.